Using Plugin Tools Java5 Annotations

Since version 3.0, you can use Java5 annotations to generate the plugin descriptor file.

NOTE With annotations, your Mojo super class does not any more require to be in the same project. Provided that the super class also uses annotations, it can now come from reactor projects or external dependencies. As javadoc doclet are still useful for @since, @deprecated and comments, the sources are still scanned. So if you use an external dependency, you must still provide an artifact with sources (sources classifier) to provide documentation (the tooling will skip error if this artifact sources is missing).


Information for plugin descriptor generation is specified using 4 annotations:

  • 2 class-level annotations:
    • @Mojo: This annotation will mark your class as a Mojo,
    • @Execute: Used if your Mojo needs to fork a lifecycle,
  • 2 field-level annotations:
    • @Parameter: Used to configure your Mojo parameters,
    • @Component: Used to configure injection of Plexus components or Maven context components.

For more information on these annotations, see the corresponding documentation.

Notice that Plugin Tools Java 5 Annotations are named after Plugin Tools Javadoc Tags with following little differences:

Plugin Tools Javadoc Tags Plugin Tools Java 5 Annotation
@goal "goal-name" @Mojo( name = "goal-name" )
@phase "<phase-name>" @Mojo( defaultPhase = LifecyclePhase.<phase> )

POM configuration

To be able to use these Java 5 annotations, you need to add some configuration to your plugin POM:

    <!-- dependencies to annotations -->
      <scope>provided</scope><!-- annotations are needed only to build the plugin -->
          <!-- see -->
          <!-- if you want to generate help goal -->