jira-importer commented on issue #968: URL: https://github.com/apache/maven-javadoc-plugin/issues/968#issuecomment-2957365434
**[Andreas Horst](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ahorst)** commented 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)? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
