[MJAVADOC-168] Regression: 2.4-SNAPSHOT does not generate docs for generates sources if run outside a build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.5
• Environment: Maven 2.0.8, JDK 1.5.0_12, WinXP
• Assignee: Siveton Vincent
• Reporter: Benjamin Bentmann
• Created: 18/Jan/08 09:04
• Updated: 02/Jan/09 05:18
• Resolved: 30/May/08 17:20

Description

The fix applied for MJAVADOC-145 causes the plugin to loose source roots that get created during the generate-sources build phase. I.e. if one runs

mvn org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc

the plugin properly documents generated source code but running

mvn org.apache.maven.plugins:maven-javadoc-plugin:2.4-SNAPSHOT:javadoc

only documents the default source root "src/main/java".

Usually, I would expect to have the JavadocReport mojo @execute phase="generate-sources" and the TestJavadocReport mojo to have @execute phase="generate-test-sources" (although it's kind of ugly to have the compile phase being run in the later case).

In lack of these annotations, the plugin produces different output when run directly from the command line or indirectly as part of build.

Issue Links

• is duplicated by: MJAVADOC-186 Multimodule javadoc aggregate fails when submodule depends on generate-sources phase being executed
• is related to: MJAVADOC-145 If Javadoc is set to aggregate, the build fails inside a Maven plugin module
• is related to: MJAVADOC-138 javadoc:test-javadoc failed if target/classes not already created
• relates to: MJAVADOC-179 Aggregate report ignores sourcepath customization of subprojects
• relates to: MJAVADOC-194 javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project