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.

		</get>
		<unzip dest="${plugins.dir}/${plugin.name}" src="${target.dir}/${plugin.name.prefix}${plugin.name}-${plugin.zip.version}.zip">
			<patternset>
				<include name="**" />
			</patternset>
			<cutdirsmapper dirs="1" />
		</unzip>
	</target>

	<target name="remove.jars" if="with.fess">
		<delete>
			<fileset dir="${plugins.dir}">

KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<plugin>
  <description>plugin-description</description>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-jar-plugin</artifactId>
  <version>2.3-SNAPSHOT</version>
  <goalPrefix>jar</goalPrefix>
  <isolatedRealm>false</isolatedRealm>

import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.plugin.descriptor.PluginDescriptor;
import org.apache.maven.api.plugin.descriptor.lifecycle.Lifecycle;

/**
 * Represents a maven plugin runtime
 *
 * @since 4.0.0
 */
@Experimental
public interface Plugin {

    @Nonnull
    org.apache.maven.api.model.Plugin getModel();

    @Nonnull
    PluginDescriptor getDescriptor();

    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>build</groupId>
          <artifactId>managed-plugin</artifactId>
          <executions>
            <execution>
              <phase>test</phase>
            </execution>
            <execution>
              <phase>test</phase>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </pluginManagement>

  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.

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>test</groupId>
          <artifactId>managed-duplicate</artifactId>
        </plugin>
        <plugin>
          <groupId>test</groupId>
          <artifactId>managed-duplicate</artifactId>
        </plugin>
      </plugins>
    </pluginManagement>
    <plugins>
      <plugin>
        <groupId>test</groupId>

  <version>0.1</version>

  <build>
    <plugins>
      <plugin>
        <groupId>test</groupId>
        <artifactId>good</artifactId>
        <version>1.0</version>
      </plugin>
      <plugin>
        <groupId>test</groupId>
        <artifactId>mip</artifactId>
        <version>${missing.property}</version>
      </plugin>
      <plugin>
        <groupId>test</groupId>
        <artifactId>rmv</artifactId>

## Quickstart

To easily try out the feature, run the included demo Access Management Plugin program in this directory:

```sh
go run access-manager-plugin.go
```

          <overrides>
            <parent-only>parent</parent-only>
            <parent>parent</parent>
          </overrides>
        </configuration>
      </plugin>
    </plugins>
  </build>

  <reporting>
    <plugins>
      <plugin>
        <artifactId>MNG-5115</artifactId>
        <reportSets>
          <reportSet>
            <id>default-inherited</id>
            <reports>