[
https://issues.apache.org/jira/browse/MJAVADOC-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957892#comment-17957892
]
Olivier Lamy commented on MJAVADOC-227:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#931|https://github.com/apache/maven-javadoc-plugin/issues/931].
> Aggregated javadocs do not take per project configuration into account
> ----------------------------------------------------------------------
>
> Key: MJAVADOC-227
> URL: https://issues.apache.org/jira/browse/MJAVADOC-227
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Carsten Ziegeler
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
