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

Peter Hendriks commented on MJAVADOC-137:
-----------------------------------------

We run the goals "clean javadoc:javadoc install", i.e. we explicitly call the 
javadoc goal. In the past when running this on a multi-module pom, this 
triggered the javadoc:javadoc goal on each module. With version 2.3, this 
triggers the [javadoc:javadoc] as (aggregator-style) on the main pom, and no 
separate javadoc is generated anymore.

I looked up the bug you linked to but I find it difficult to relate this to 
this problem. I tried looking up some documentation about @aggregator, but it 
is not described in the Mojo documentation. I agree with you that the 
@aggregator seems at odds with the "aggregate" property, but it may be my lack 
of understanding this feature. 

Do you know where I can find more information about how aggregator is supposed 
to work, and if there are work-arounds to disable aggregator-style? 

> 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

        

Reply via email to