[
http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120477
]
Benjamin Bentmann commented on MJAVADOC-137:
--------------------------------------------
I must confess I still could not figure out how exactly [EMAIL PROTECTED]
affects the plugin's execution, the Mojo API is quite short about this. If
there are use-cases that require this annotation, then it might be worth to
consider splitting mojos into two: one that has [EMAIL PROTECTED] and one that
has not. This way, the user can choose the appropriate mojo. The [Assembly
Plugin|http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html]
uses this approach, too.
> 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
