[MNG-4618] maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-7
• Fix Version/s: 3.0-beta-1
• Component/s: Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Bob Paulin
• Created: 03/Apr/10 14:34
• Updated: 03/Jan/14 12:18
• Resolved: 06/Apr/10 06:00

Description

Binding javadoc:aggregate-jar to package in an aggregator project works with maven 2.

In maven3, it attempts to build the aggregate javadocs before completing the full reactor.

When executing 'mvn install', I'd expect it to run the reactor and install all modules before attempting the 'compile' dependency resolution for the javadoc execution.

During early execution, I get output such as:

[WARNING] The dependency: [org.torquebox:torquebox-common-spi:jar:1.0.0.Beta19] can't be resolved but has been found in the reactor (probably snapshots).
This dependency has been excluded from the Javadoc classpath. You should rerun javadoc after executing mvn install.

In maven2, it'd react, install all submodules, then, as the last act, do the javadoc:aggregate-jar.

If I add a <dependency> for each module to the maven-javadoc-plugin's <dependencies> section, then it will get the order correct. I'd just kinda think that'd be implicit.