[
http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122843
]
Dan Fabulich commented on MJAVADOC-137:
---------------------------------------
I'm pretty sure MNG-2184 is to blame here; it seems clear that reporting
plugins that use forked lifecycles should not use @aggregator. At least in
this case, it seems to be harmful and unnecessary.
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.
http://www.nabble.com/%40aggregator-mojo-annotation-td15302246s177.html
> javadoc:javadoc always runs as "aggregator"
> -------------------------------------------
>
> Key: MJAVADOC-137
> URL: http://jira.codehaus.org/browse/MJAVADOC-137
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Peter Hendriks
> Priority: Critical
> Fix For: 2.4
>
>
> In version 2.2, javadoc aggregation was configurable using the configuration
> property "aggregate". In version 2.3, all javadoc goals got the @aggregator
> attribute added to its mojos (through a change in
> org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java), and the goals now
> always run aggregated regardless of the configuration setting. This breaks
> our build as we require non-aggregated javadoc execution in our multi-module
> poms. Please fix this so this is once again configurable and backwards
> compatible with previous versions of the javadoc plug-in.
--
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
