[ 
http://jira.codehaus.org/browse/MJAVADOC-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183722#action_183722
 ] 

Brian Fox commented on MJAVADOC-227:
------------------------------------

I'll add further clarification: The javadoc aggregate goal is, surprisingly, an 
aggregator. This means unlike normal goals that cause maven to iterate over 
each project, this one runs just once. It asks maven ahead of time to resolve 
all the projects in the reactor and it gets a list of them injected. The plugin 
configuration however comes from the project where it's being executed. 
Therefore, the configuration you have in all the sub modules is completely 
irrelevant as the only thing in context for configuration is the root project. 
If you want it to exclude certain things, you need to configure it here in the 
root or the plugin won't see it at all.

> Aggregated javadocs do not take per project configuration into account
> ----------------------------------------------------------------------
>
>                 Key: MJAVADOC-227
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-227
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5
>            Reporter: Carsten Ziegeler
>
> We have a multi project setup where each module has a configuration for the 
> javadocs for excluding packages.
> Building the javadocs for each project separately works fine.
> Starting the build from the root and building aggregated javadocs there, 
> results in javadocs for all sources. The exclude package configurations of 
> the individual poms are not considered.
> I've used "javadoc:javadoc" to build the docs and tried both, putting the 
> config in the plugin section and the reporting section in each module.
> A workaround is of course to manually configure the javadoc plugin in the 
> root pom and copy all excludes from the modules there; but that's a 
> maintenance nightmare.

-- 
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