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

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

                    <build>
                        <plugins>
                            <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-exec-plugin</artifactId>
                                <version>${exec.plugin.version}</version>
                            </plugin>
                        </plugins>
                    </build>

    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]jvm[/\\]plugins-jvm-test-suite[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]plugins[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"

import static eu.maveniverse.domtrip.maven.MavenPomElements.Plugins.DEFAULT_MAVEN_PLUGIN_GROUP_ID;
import static eu.maveniverse.domtrip.maven.MavenPomElements.Plugins.MAVEN_4_COMPATIBILITY_REASON;
import static eu.maveniverse.domtrip.maven.MavenPomElements.Plugins.MAVEN_PLUGIN_PREFIX;

/**
 * Strategy for upgrading Maven plugins to recommended versions.
 * Handles plugin version upgrades in build/plugins and build/pluginManagement sections.
 */
@Named

                            </plugin>
                        </plugins>
                        <pluginManagement>
                            <plugins>
                                <plugin>
                                    <groupId>org.apache.maven.plugins</groupId>
                                    <artifactId>maven-compiler-plugin</artifactId>

        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>create-distribution-in-dir</id>
      <activation>
        <property>
          <name>distributionTargetDir</name>
        </property>
      </activation>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>

        // The plugins option itself won't be set, but the logic in BaseUpgradeGoal
        // should treat --all as enabling plugins
        assertFalse(options.plugins().isPresent(), "--plugins option should not be explicitly set when using --all");
    }

    @Test
    void testLongFormPluginsOption() throws ParseException {
        String[] args = {"apply", "--plugins"};

  {
    "name": "plugins-application",
    "path": "platforms/jvm/plugins-application",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "plugins-distribution",
    "path": "platforms/software/plugins-distribution",
    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "plugins-groovy",

        assertNotNull(plugin, "Should create plugin element");

        String xmlOutput = DomUtils.toXml(doc);
        assertTrue(xmlOutput.contains("<plugin>"), "Should contain plugin element");
        assertTrue(xmlOutput.contains("<groupId>org.apache.maven.plugins</groupId>"), "Should contain groupId");