[
http://jira.codehaus.org/browse/MPLUGIN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144534#action_144534
]
Vincent Siveton commented on MPLUGIN-56:
----------------------------------------
I think this issue was already fix somewhere... See generated documentation.
http://maven.apache.org/plugins/maven-javadoc-plugin-2.5/javadoc-mojo.html
{noformat}
* 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.
{noformat}
http://maven.apache.org/plugins/maven-javadoc-plugin-2.5/aggregate-mojo.html
{noformat}
* 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.
{noformat}
> Inter-plugin Mojo inheritance
> -----------------------------
>
> Key: MPLUGIN-56
> URL: http://jira.codehaus.org/browse/MPLUGIN-56
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Reporter: Kohsuke Kawaguchi
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
