<phase>process-classes</phase>
            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <instructions>
            <!-- Silence a warning that claims that META-INF/versions/9/... is the "wrong directory" for our classes. -->
            <_fixupmessages>^Classes found in the wrong directory: .*</_fixupmessages>

  ]]></description>

  <defaults>
    <default>
      <key>package</key>
      <value>org.apache.maven.cli.internal.extension.model</value>
    </default>
  </defaults>

  <classes>
    <class rootElement="true" xml.tagName="extensions" xsd.compositor="sequence">
      <name>CoreExtensions</name>
      <description>Extensions to load.</description>
      <version>1.0.0+</version>
      <fields>

import org.apache.maven.api.annotations.Nullable;

/**
 * {@code ArtifactCoordinates} completed with information about how the artifact will be used.
 * This information includes the dependency type (main classes, test classes, <i>etc.</i>),
 * a scope (compile, runtime <i>etc.</i>), an obligation (whether the dependency
 * is optional or mandatory), and possible exclusions for transitive dependencies.

import org.jspecify.annotations.NullUnmarked;

/** Basic sanity tests for classes in {@code common.base}. */

@J2ktIncompatible
@GwtIncompatible
@NullUnmarked
public class PackageSanityTests extends AbstractPackageSanityTests {
  public PackageSanityTests() {
    // package private classes like FunctionalEquivalence are tested through the public API.
    publicApiOnly();
  }

#    'com.missing.dependency.WTF',
#    // ...
#   ]
#
# Wildcards are not allowed, excludes must be exact. The build also fails with
# the message "Invalid exclusions, nothing is wrong with these classes" if
# extraneous classes are in the excludes list, this ensures the list is
# up-to-date, and that each module accurately documents the evil things
# that its dependencies do.
#

        buf.append("},");
        final Classes classes = jvmStats.getClasses();
        buf.append("\"classes\":{");
        append(buf, "loaded", () -> classes.getLoadedClassCount()).append(',');
        append(buf, "total_loaded", () -> classes.getTotalLoadedClassCount()).append(',');
        append(buf, "unloaded", () -> classes.getUnloadedClassCount());
        buf.append("},");

 * implementing new escapers. It is strongly recommended that when implementing a new escaper you
 * extend one of these classes. If you find that you are unable to achieve the desired behavior
 * using either of these classes, please contact the Java libraries team for advice.
 *
 * <p>Popular escapers are defined as constants in classes like {@link
 * com.google.common.html.HtmlEscapers} and {@link com.google.common.xml.XmlEscapers}. To create

        jvmThreadsObj.peak = threads.getPeakCount();
        final Classes classes = jvmStats.getClasses();
        final JvmClassesObj jvmClassesObj = new JvmClassesObj();
        jvmObj.classes = jvmClassesObj;
        jvmClassesObj.loaded = classes.getLoadedClassCount();
        jvmClassesObj.total_loaded = classes.getTotalLoadedClassCount();
        jvmClassesObj.unloaded = classes.getUnloadedClassCount();

        assertEquals(str, result);
    }

    /**
     * Test that default filter allows org.codelibs classes
     *
     * @throws Exception
     */
    public void testFromBinaryToObject_DefaultFilter_AllowsCodelibsClasses() throws Exception {
        // The default filter should allow org.codelibs.* classes
        final TestSerializableClass obj = new TestSerializableClass("test", 456);

~~ under the License.

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2016-05-29
 -----

Maven Compat

 Maven2 classes maintained as compatibility layer for plugins that need to keep Maven2 compatibility.

 Plugins should avoid these classes and be updated to use only Maven3 dependencies (and require Maven3): see