META-INF/maven/plugin.xml A test plugin to assist testing of Maven core. org.apache.maven.plugins maven-surefire-plugin 0.1 surefire false true test Does nothing. test false true false false false true org.apache.maven.plugin.coreit.ItMojo java per-lookup once-per-session org.apache.maven maven-plugin-api jar 2.0 org/apache/maven/plugin/coreit/ItMojo.class package org.apache.maven.plugin.coreit; public synchronized class ItMojo extends org.apache.maven.plugin.AbstractMojo { public void ItMojo(); public...

1.6.0_07 META-INF/maven/plugin.xml A test plugin to assist testing of Maven core. org.apache.maven.plugins maven-jar-plugin 0.1 jar false true jar Does nothing. runtime false true false false false true org.apache.maven.plugin.coreit.ItMojo java per-lookup once-per-session org.apache.maven maven-plugin-api jar 2.0 org/apache/maven/plugin/coreit/ItMojo.class package org.apache.maven.plugin.coreit; public synchronized class ItMojo extends org.apache.maven.plugin.AbstractMojo { public void ItMojo(); public...

  xml.schemaLocation="https://maven.apache.org/xsd/repository-metadata-${version}.xsd">
  <id>repository-metadata</id>
  <name>Metadata</name>
  <description><![CDATA[
    <p>Per-directory repository metadata <code>repository-metadata.xml</code>.</p>
    <p>A directory may represent 3 types of content: "groupId", "groupId/artifactId" or "groupId/artifactId/version".</p>

META-INF/MANIFEST.MF Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: joakim Build-Jdk: 1.4.2_12 META-INF/plexus/components.xml org.apache.maven.wagon.Wagon dav org.apache.maven.wagon.providers.webdav.WebDavWagon per-lookup META-INF/LICENSE.txt Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and...

    private List<String> pluginGroups;

    private boolean isProjectPresent = true;

    // ----------------------------------------------------------------------------
    // We need to allow per execution user and global settings as the embedder
    // might be running in a mode where it's executing many threads with totally
    // different settings.

commons-logging.jar to be shared in a multiple class loader environment (such as a servlet container), but still allow each web application to provide its own LogFactory implementation, if it so desires. An instance of this class will then be created, and cached per class loader. The Default LogFactory Implementation The Logging Package APIs include a default LogFactory implementation class ( org.apache.commons.logging.impl.LogFactoryImpl) that is selected if no other implementation class name can be discovered....

          <version>1.0.0+</version>
          <description>
            Configuration of server-specific settings, mainly authentication
            method. This allows configuration of authentication on a per-server
            basis.
          </description>
          <association>
            <type>Server</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>

     * This map is usually either empty if no module was found, or a singleton map.
     * It may however contain more than one entry if module hierarchy was detected,
     * in which case there is one key per sub-directory.
     *
     * <p>This map may contain null values if the constructor was invoked with {@code resolve}
     * parameter set to false. This is more efficient when only the module existence needs to

    <component>
      <role>org.apache.maven.wagon.Wagon</role>
      <role-hint>testfile</role-hint>
      <implementation>org.apache.maven.artifact.resolver.TestFileWagon</implementation>
      <instantiation-strategy>per-lookup</instantiation-strategy>
    </component>
  </components>

    @Inject
    public DefaultLifecycleProvider() {
        super(
                LIFECYCLE_ID,
                PHASES,
                null // no global plugin bindings for default lifecycle: they are defined per-packaging in separate
                // providers
                );
    }