[jira] Closed: (MJAVADOC-227) Aggregated javadocs do not take per project configuration into account

["Vincent Siveton (JIRA)" <ji...@codehaus.org>]

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

Vincent Siveton closed MJAVADOC-227.
------------------------------------

    Resolution: Not A Bug

IIUC you want to run javadoc:aggregate from root and use the subproject plugin configuration: it is not possible (maven core) and I close it.

I suggest you to add properties to exclude your packages in the root and use them in the sub projects.

> 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