| provides a specific path to the Tomcat instance. To use this, your plugin configuration might
     | hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |

                    <build>
                        <plugins>
                            <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-compiler-plugin</artifactId>
                                <version>3.13.0</version>
                            </plugin>
                        </plugins>
                    </build>
                </project>

        </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"};

- we have to deal with scripting implementations (groovy, beanshell, ruby)
- we need to deal with a shared context for plugins, like the guarded mojos
- we need to deal with plugins as core application logic which can also interact with plugins

* Along with this comes the testing strategies that make this work
* The repository model where plugins can be stored and cataloged
* Bridging this into an OSGi system: if this could be done then we can basically take over p2

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

                    Arguments.of(null, null, "4.1.0", false, "Should disable plugins when only --model-version is set"),
                    Arguments.of(false, null, null, false, "Should disable plugins when --all=false"),
                    Arguments.of(null, null, null, true, "Should enable plugins by default when no options specified"));
        }
    }

                List<org.apache.maven.artifact.repository.metadata.Plugin> plugins = pluginGroupMetadata.getPlugins();

                if (plugins != null) {
                    for (org.apache.maven.artifact.repository.metadata.Plugin plugin : plugins) {
                        if (request.getPrefix().equals(plugin.getPrefix())

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
@Singleton
@Priority(10)
public class PluginUpgradeStrategy extends AbstractUpgradeStrategy {

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/org/apache/maven/plugins/coreit/AMojo.java package org.apache.maven.plugin.coreit; /* * Licensed to the Apache...