Affects Version/s: 2.6.1
Fix Version/s: 2.8
Number of attachments :
I have an aggregate project. In pluginManagement, I spec out javadoc:jar. In the leaf projects, I turn it on with an ordinary <plugin/> for the plugin.
If I leave detectOfflineLinks with its default value of true, the javadoc plugin uses the invoker plugin to relaunch itself, recursively, complaining that it hasn't been run on one or another of the projects. Note that, when this happens, it is 'swimming upstream' – it is processing project A, it invokes itself on project B, where B depends on A, not the other way around.
If I run maven just in the leaf directories all is well. The trouble only happens when running maven from the aggregating parent.
Just to clarify, in case I don't get a test case together too soon ...
javadoc only mentioned in the <reporting> section.
javadoc only mentioned in pluginManagement, setting up execution of javadoc:jar.
A very plain 'plugin' element just to turn on the configuration from plugin management.
mvn run from leaf: all is well.
mvn run from aggregating parent: lots of extra 'invoker' invocations of javadoc on projects that have dependencies on the current project.