jira-importer commented on issue #968: URL: https://github.com/apache/maven-javadoc-plugin/issues/968#issuecomment-2957365433
**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented IMHO, it's about m-javadoc-p having 4 goals, each having `@requiresDependencyResolution` compile and the way Maven core needs to actually **run** scopes to do the resolution, and it does it multiple times I still don't understand everything, nor have an idea if it's a bug or unexpected consequence of a feature but it lead me to a workaround: if you define reportSets with less than the 4 reports, you'll divide the number of executions if you configure javadoc report only, without test-javadoc or aggregate versions like this: ```xml <plugin> <artifactId>maven-javadoc-plugin</artifactId> <version>2.8</version> <reportSets> <reportSet> <reports> <report>javadoc</report> </reports> </reportSet> </reportSets> </plugin> ``` the multiple executions will disappear (and a lot of m-javadoc-p version will simply blow up, I didn't study why, just came to the conclusion that new versions have less bugs than old ones) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
