What is the implicit ID of a maven plugin execution?

by

By default, Maven will create an execution id applying the following patterns depending on different cases:

  • Execution id set to: default-cli for plugin:goals executed from the command line
  • Execution id set to: default-<goal_name> for plugin:goals executed as part of the binding defined by a specific packaging
  • Execution id set to: default for plugin:goals executions as part of the POM which didn’t specify any id.

If you execute the Maven Dependency Plugin from the command line, for instance, with the classic mvn dependency:tree goal, you will notice the default-cli execution id:

[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ project ---

If you look at the output of any Maven build and at the default executions for the Maven Compiler Plugin during the compile phase, for instance, you will notice default-compile and default-testCompile as execution ids of the compile and testCompile goals of the Maven Compiler Plugin.

The same pattern is applied to all default plugins/goals executed by Maven as part of the binding defined for a given packaging. Execution ids are always between curved brackets right after the concerned plugin and goal name.
For instance, an extract of a basic Maven build: 

[INFO] --- maven-clean-plugin:2.5:clean (default-clean)
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) 
[INFO] --- maven-surefire-plugin:2.19:test (default-test)

Shows how the execution ids (last token in the snippet above, between brackets) are always following this pattern.

Finally, if you configure an execution of any plugin in your POM without specifying an id, you will notice the default id applied by Maven:

[INFO] --- exec-maven-plugin:1.1:java (default) @ project ---

From official Maven documentation:

Command line execution id

each mojo invoked directly from the command line will have an execution Id of default-cli assigned to it, which will allow the configuration of that execution from the POM by using this default execution Id

Default binding execution id

each mojo bound to the build lifecycle via the default lifecycle mapping for the specified POM packaging will have an execution Id of default-goalName assigned to it

Default plugin execution id

the default value of the executionId – literally set to default in the POM model – was meant to provide some of this functionality. Unfortunately, this solution was never tested to make sure it worked with the use cases above; they fell through the cracks during testing. Now, with the release of Maven 2.2.0 (and later, Maven 3.0), these use cases can finally be addressed

Last but not least, concerning execution ids, since Maven 3.3.1 you can even point to a particular execution id of your POM from the command line using the new @executionId operator

More Related Contents:

  1. What is pluginManagement in Maven’s pom.xml?
  2. How do you specify the Java compiler version in a pom.xml file?
  3. How to refer environment variable in POM.xml?
  4. stop IntelliJ IDEA to switch java language level every time the pom is reloaded (or change the default project language level)
  5. Maven BOM [Bill Of Materials] Dependency
  6. Display omitted versions in maven dependency:tree?
  7. What is the difference between “pom” type dependency with scope “import” and without “import”?
  8. Is there anyway to exclude artifacts inherited from a parent POM?
  9. How to use POMs as a dependency in Maven?
  10. repository element was not specified in the POM inside distributionManagement element or in -DaltDep loymentRepository=id::layout::url parameter
  11. IntelliJ – Convert a Java project/module into a Maven project/module
  12. Maven adding mainClass in pom.xml with the right folder path
  13. What does mvn install in maven exactly do
  14. Difference between and tag in Maven `pom.xml` [duplicate]
  15. Maven not picking JAVA_HOME correctly
  16. What exactly is a Maven Snapshot and why do we need it?
  17. No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
  18. Running junit tests in parallel in a Maven build?
  19. Maven Run Project
  20. Get source JARs from Maven repository
  21. Why is my URI not hierarchical? [duplicate]
  22. Maven Compilation Error: (use -source 7 or higher to enable diamond operator)
  23. What does Maven do, in theory and in practice? When is it worth to use it? [closed]
  24. Which artifacts should I use for JAXB RI in my Maven project?
  25. java.lang.NoClassDefFoundError: org/springframework/core/env/ConfigurableEnvironment
  26. Environment Variable with Maven
  27. Java.lang.NoClassDefFoundError: com/fasterxml/jackson/databind/exc/InvalidDefinitionException
  28. Maven Resource Filtering with Spring Boot: Could not resolve placeholder
  29. Maven dependency resolution (conflicted)
  30. Hibernate, Java 9 and SystemException

Leave a Comment