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();

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

<plugin>
  <description>Maven Internal State-Management Plugins</description>
  <groupId>org.apache.maven.plugins.internal</groupId>
  <artifactId>maven-state-management</artifactId>
  <version>2.1</version>
  <goalPrefix>statemgmt</goalPrefix>
  <isolatedRealm>false</isolatedRealm>

  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.

// See the License for the specific language governing permissions and
// limitations under the License.

// This is a sample chained plugin that supports multiple CNI versions. It
// parses prevResult according to the cniVersion
package plugin

import (
	"context"
	"encoding/json"
	"fmt"
	"runtime/debug"
	"strconv"
	"time"

	"github.com/containernetworking/cni/pkg/skel"

		<get dest="${target.dir}">
			<url url="${repo.url}/${plugin.groupId}/${plugin.name.prefix}${plugin.name}/${plugin.version}/${plugin.name.prefix}${plugin.name}-${plugin.zip.version}.zip" />
		</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>

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-plugin-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>

permissions and limitations * under the License. */ import org.apache.maven.plugin.AbstractMojo; /** * Does nothing. * * @goal addPluginArtifactMet * * @author Benjamin Bentmann */ public class TestMojo extends AbstractMojo { public void execute() { } } META-INF/maven/org.apache.maven.plugins/maven-plugin-plugin/pom.xml 4.0.0 org.apache.maven.plugins maven-plugin-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...

  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.

                                            <tr>
                                                <th><la:message key="labels.plugin_type"/></th>
                                                <th><la:message key="labels.plugin_name"/></th>
                                                <th><la:message key="labels.plugin_version"/></th>
                                                <th></th>
                                            </tr>

bo <bo@TeamCity> 1621304116 +0200