[
http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103388
]
John Allen commented on MJAVADOC-137:
-------------------------------------
If you run the javadoc plugin as report then the @aggregator is ignored (see
MNG-2184), I have removed the @aggregator from my local version of the plugin
and it passes all its tests but i expect the JavadocJarMojo might suffer
(haven't tested yet and i would have too look at the code some more).
Personally I cant see why one would want any of the javadoc mojo's
functionality to run as an aggregator. Note the 'aggregate' report mojo option
is actually implemented inside the mojo, ie. the report exits if it's already
been run in the reactor and aggregate is true.
> 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
