[MJAVADOC-284] detectOfflineLinks sets off extra spurious executions of javadoc

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.1
• Fix Version/s: 2.8
• Assignee: Herve Boutemy
• Reporter: Benson Margulies
• Created: 04/May/10 08:42
• Updated: 25/Apr/11 03:33
• Resolved: 12/Jan/11 17:56

Description

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 ...

external/corporate parent:

javadoc only mentioned in the <reporting> section.

aggregating parent:

javadoc only mentioned in pluginManagement, setting up execution of javadoc:jar.

leaf:

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.

Issue Links

• is duplicated by: MJAVADOC-295 javadoc plugin version: 2.5, 2.6, 2.7 does not follow the reactor build sequence "mvn install site site:deploy"
• is related to: MJAVADOC-286 Version 2.7 in Maven Reactor may cause infinite recursion, symptoms similar to MJAVADOC-268
• is related to: MJAVADOC-181 Javadoc report not generated for multi-module project if run from parent level.
• relates to: MJAVADOC-268 performance problem in AbstractJavadocMojo.getModulesLinks()
• relates to: MJAVADOC-275 Creation of Javadoc attachments fails in multi-module project where modules have never been installed/deployed