[
http://jira.codehaus.org/browse/MJAVADOC-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MJAVADOC-168:
---------------------------------------
Attachment: MJAVADOC-168.zip
Here's a test project to play with. When invoking "mvn javadoc:javadoc" only
the class "Main" makes it into the api docs. If you invoke "mvn compile" (where
I added an execution of the javadoc plugin), you get both "Main" and
"GeneratedClass".
If the @execute annotation really cannot be re-added due to MJAVADOC-145, there
must at least be some doc/faq about this odd behavior. However, I currently do
not believe that @execute was the real cause of this other issue. I would
rather ask why the mojo has @phase generate-sources as annotation. The Javadoc
Plugin does not really participate in the default build cycle, its usually part
of the site lifecycle.
> Regression: 2.4-SNAPSHOT does not generate docs for generates sources if run
> outside a build
> --------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-168
> URL: http://jira.codehaus.org/browse/MJAVADOC-168
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Maven 2.0.8, JDK 1.5.0_12, WinXP
> Reporter: Benjamin Bentmann
> Attachments: MJAVADOC-168.zip
>
>
> 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
> {noformat}
> mvn org.apache.maven.plugins:maven-javadoc-plugin:2.3:javadoc
> {noformat}
> the plugin properly documents generated source code but running
> {noformat}
> mvn org.apache.maven.plugins:maven-javadoc-plugin:2.4-SNAPSHOT:javadoc
> {noformat}
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
