xml.namespace="http://maven.apache.org/PLUGIN/${version}"
  xml.schemaLocation="https://maven.apache.org/xsd/plugin-${version}.xsd">
  <id>plugin</id>
  <name>PluginDescriptor</name>
  <description><![CDATA[
    Maven 4 Plugin descriptor, stored in {@code META-INF/maven/plugin.xml} in a plugin's jar artifact.
    This descriptor is generally using the information contained in the annotations of the plugin api.

  the component descriptor and when it's loaded we can add the discoverer, that would be simpler. I could
  also do this with the lister as well
i'l
// 1 the metadata -> model plugin/mojo descriptor
// 2 tools for doing the mapping
// 3 the component model -> interfaces for the plugin

// The plugin manager should load up a directory structure of plugins.

maven-clean-plugin 2.0-rc2-SNAPSHOT maven-compiler-plugin 2.0-beta-2-SNAPSHOT maven-deploy-plugin 2.0-beta-1 true true maven-install-plugin 2.0-beta-2-SNAPSHOT maven-jar-plugin 2.0-rc2-SNAPSHOT maven-javadoc-plugin 2.0-beta-2-SNAPSHOT attach-javadocs jar true maven-resources-plugin 2.0-beta-2 maven-source-plugin 2.0-rc1 attach-sources jar true maven-surefire-plugin 2.0-beta-2-SNAPSHOT false snapshots Maven Central Development Repository http://snapshots.maven.codehaus.org/maven2 false central Maven Repository Switchboard...

org.apache.maven.plugin.coreit; public synchronized class ItMojo extends org.apache.maven.plugin.AbstractMojo { public void ItMojo(); public void execute(); } pom.xml 4.0.0 org.apache.maven.its.plugins maven-it-plugin 0.1 maven-plugin Maven Integration Test Plugin A test plugin to assist testing of Maven core. 2009 maven-core-it file:///${basedir}/repo true true org.apache.maven maven-plugin-api 2.0 . pom.xml src/** src/main/resources src/main/java/org/apache/maven/plugins/coreit/AMojo.java src/main/java/...

          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-assembly-plugin</artifactId>
          <version>2.2-beta-2</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-resources-plugin</artifactId>
          <version>2.4-SNAPSHOT</version>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

            }

            if ( !found )
            {
                Plugin mappedPlugin = new Plugin();

                mappedPlugin.setArtifactId( plugin.getArtifactId() );

                mappedPlugin.setPrefix( plugin.getPrefix() );

                mappedPlugin.setName( plugin.getName() );

                addPlugin( mappedPlugin );

                changed = true;
            }

                }
                // Plugins
                for (ReportPlugin plugin : reporting.getPlugins()) {
                    visit(plugin);
                }
            }
        }

        private void visit(ReportPlugin plugin) {
            if (plugin != null) {
                String org, val;
                // Inherited
                org = plugin.getInherited();

            <goals>
              <goal>velocity</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-jar-plugin</artifactId>
        <configuration>
          <archive>
            <manifest>
              <mainClass>org.apache.maven.cling.MavenCling</mainClass>

For external plugins, it's difficult for an object to be used outside the application of a plugin, so following best practices is relatively straightforward.  For core plugins in gradle/gradle, it's easy for an object to be created without applying its associated plugin. For instance, Spring has a plugin that uses the Checkstyle task directly without applying the Checkstyle plugin.

 *   <li><strong>maven-remote-resources-plugin</strong>: Upgrades to version 3.0.0 or higher</li>
 * </ul>
 * Plugin versions are upgraded in both {@code <build><plugins>} and {@code <build><pluginManagement><plugins>} sections.
 * If a plugin version is defined via a property, the property value is updated instead.
 *
 * <h3>Inference Optimizations (Optional)</h3>