{
  "name": "k8s-pod-network",
  "cniVersion": "0.3.1",
  "pugins": [
    {
      "type": "calico",
      "etcd_endpoints": "http://10.110.0.136:6666",
      "log_level": "info",
      "mtu": 1500,
      "ipam": {
        "type": "calico-ipam"
      },
      "policy": {
        "type": "k8s"
      },
      "kubernetes": {
        "kubeconfig": "/etc/cni/net.d/calico-kubeconfig"
      }
    },
    {

            |
   [plexus.core.maven]
     ^            ^
     |            |
[plugin0]      [plugin1]
+-----+

 The <<<plexus.core>>> realm contains the resources required to run any
 plexus application; The <<<plexus.core.maven>>> realm contains all of the
 resources required to run Maven. Each subsequent plugin realm contains the
 JAR plugin as well as its dependencies. The realms noted above are setup

		<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>

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>

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...

 *
 * h3. lookup the plugin with a configuration
 *
 * h3. execute the plugin
 *
 * h3. plugins may have to deal with particular actions when a plugin is - installed - loaded -
 * unloaded - update - uninstalled
 *
 * h3. plugins should be able to have specific metadata for a plugin model and that be translated -
 * dependencies - resources - configuration - extension points of plugins
 *

  <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>

<project>
    <modelVersion>4.0.0</modelVersion>
    <groupId>tests.project</groupId>
    <artifactId>duplicate-plugin-defs-merged</artifactId>
    <version>1</version>

    <build>
      <plugins>
        <plugin>
          <artifactId>maven-compiler-plugin</artifactId>
          <dependencies>
            <dependency>
              <groupId>group</groupId>
              <artifactId>first</artifactId>
              <version>1</version>

     1. plugin goal execution in a child is usually simply appended (at end): you can't try to insert in the middle of pre-existing inherited executions,

     2. append happens at plugin level first, then goal level, independently from phases.
        This means for example that adding pluginA:goal2 to pre-existing (pluginA:goal1, pluginB:goal) will lead to (pluginA:goal1, pluginA:goal2, pluginB:goal)

  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.