[
https://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323750#comment-323750
]
Andreas Horst commented on MJAVADOC-171:
----------------------------------------
We are having similar issues, which are related both to the way module builds
are forked for scope resolutions and the javadoc-plugin. Simply put, some of
the modules are forked to often. For instance, we have a project with 3 modules
and a simple 'mvn clean site' leads to one of the modules being forked in every
build, i.e. the parent and ALL 3 modules; YES, it even forks itself. How is
this possible? We only use the 'aggregate' goal of the javadoc-plugin defined
in the parent POM and according to the log that's what causing this odd forks.
Maybe this is related to
[MSHARED-266|http://jira.codehaus.org/browse/MSHARED-266]?
> Modules in multi-module projects are "built" too often
> ------------------------------------------------------
>
> Key: MJAVADOC-171
> URL: https://jira.codehaus.org/browse/MJAVADOC-171
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Maven 2.0.8, Linux
> Reporter: Stefan Seidel
> Attachments: 2.2.log, 2.3.log, mjavadoc-171-b.zip, mjavadoc171.patch,
> mjavadoc-171.zip, mvnexec.zip
>
>
> In a multi-module project, all modules are "built" twice for each module.
> This leads to huge performance problems when many modules are in a project.
> In the attached sample project, the xmlbeans plugin is executed 27 times for
> a project with one parent module and two submodules. 18 of these executions
> can be attributed to the javadoc plugin. With version 2.2, only 3 invocations
> (once for each project) are caused by the javadoc plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
