[
http://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich updated MJAVADOC-171:
----------------------------------
Attachment: mjavadoc171.patch
FYI, I can't get maven-javadoc-plugin to "mvn install" from trunk (I get test
failures), but the 2.3 tag builds just fine; when I remove the @aggregator tag
from the mojo, it seems to work perfectly. I hypothesize that @aggregator is
seriously broken, at least for reporting plugins (or perhaps just plugins that
need to @execute forked lifecycles like this one), and at least in this case,
it seems to be harmful and unnecessary.
http://www.nabble.com/%40aggregator-mojo-annotation-td15302246s177.html
> Modules in multi-module projects are "built" too often
> ------------------------------------------------------
>
> Key: MJAVADOC-171
> URL: http://jira.codehaus.org/browse/MJAVADOC-171
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Maven 2.0.8, Linux
> Reporter: Stefan Seidel
> Priority: Critical
> Attachments: 2.2.log, 2.3.log, mjavadoc171.patch, mvnexec.zip
>
>
> In a multi-module project, all modules are "built" twice for each module.
> This leads to huge performance problems when many modules are in a project.
> In the attached sample project, the xmlbeans plugin is executed 27 times for
> a project with one parent module and two submodules. 18 of these executions
> can be attributed to the javadoc plugin. With version 2.2, only 3 invocations
> (once for each project) are caused by the javadoc plugin.
--
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
