MNG-3042 Extending a Mojo Class and used in a new Mojo Project, parameter fields in the parent mojo are not set, this disables reuse of existing mojo project.
It's often desirable to create a new mojo by extending an existing mojo and changing its behavior. For example, one might imagine a NetBeans plugin packager that extends from JarMojo and adds extra stuff into the jar.
Today, if I extends a mojo from another plugin, the plugin:descriptor goal fails to create a proper META-INF/maven/plugin.xml — it doesn't list any of the injections that need to happen for the base class.
Description
It's often desirable to create a new mojo by extending an existing mojo and changing its behavior. For example, one might imagine a NetBeans plugin packager that extends from JarMojo and adds extra stuff into the jar.
Today, if I extends a mojo from another plugin, the plugin:descriptor goal fails to create a proper META-INF/maven/plugin.xml — it doesn't list any of the injections that need to happen for the base class.
* Requires a Maven 2.0 project to be executed.
* Requires dependency resolution of artifacts in scope: compile.
* Since version: 2.0.
* Invokes the execution of the lifecycle phase generate-sources prior to executing itself.
* Requires a Maven 2.0 project to be executed.
* Executes as an aggregator plugin.
* Requires dependency resolution of artifacts in scope: compile.
* Since version: 2.5.
* Invokes the execution of the lifecycle phase generate-sources prior to executing itself.
* Requires a Maven 2.0 project to be executed.
* Requires dependency resolution of artifacts in scope: compile.
* Since version: 2.0.
* Invokes the execution of the lifecycle phase generate-sources prior to executing itself.
* Requires a Maven 2.0 project to be executed.
* Executes as an aggregator plugin.
* Requires dependency resolution of artifacts in scope: compile.
* Since version: 2.5.
* Invokes the execution of the lifecycle phase generate-sources prior to executing itself.
Vincent, this issue is about inheritance between mojos from different plugins which is not possibly right now as it would require to scan the sources of another plugin's dependencies to get all the javadoc annotations of the inherited stuff.
Benjamin Bentmann added a comment - 08/Aug/08 03:01 PM Vincent, this issue is about inheritance between mojos from different plugins which is not possibly right now as it would require to scan the sources of another plugin's dependencies to get all the javadoc annotations of the inherited stuff.
Improvement
Open
Major
Inter-plugin Mojo inheritance
http://maven.apache.org/plugins/maven-javadoc-plugin-2.5/javadoc-mojo.html
* Requires a Maven 2.0 project to be executed. * Requires dependency resolution of artifacts in scope: compile. * Since version: 2.0. * Invokes the execution of the lifecycle phase generate-sources prior to executing itself.http://maven.apache.org/plugins/maven-javadoc-plugin-2.5/aggregate-mojo.html
* Requires a Maven 2.0 project to be executed. * Executes as an aggregator plugin. * Requires dependency resolution of artifacts in scope: compile. * Since version: 2.5. * Invokes the execution of the lifecycle phase generate-sources prior to executing itself.