You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/03/06 03:36:28 UTC

[jira] Closed: (MJAVADOC-137) javadoc:javadoc always runs as "aggregator"

     [ http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak closed MJAVADOC-137.
--------------------------------

    Resolution: Fixed

> 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