[
http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103491
]
John Allen commented on MJAVADOC-137:
-------------------------------------
My observation should have been that when report MOJOs are run from the site
plugin they do not honour @aggregator declaration, this is what brett is
confirming [here|http://jira.codehaus.org/browse/MNG-2184#action_62425].
Running the MOJO external to site (i.e. via the command line javadoc:javadoc)
appears, according to your experiences, to allow the MOJO to run as an
aggregator. I would raise this issue on the @dev list and ask why has this MOJO
been made an @aggregator, seems like a mistake to me too. As a workaround
either drop back a version or build your own patched version of the plugin?
> 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
>
> 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
