|
Sort Order:
Benjamin Bentmann made changes - 18/Jan/08 09:05 AM
Benjamin Bentmann made changes - 18/Jan/08 09:05 AM
Benjamin Bentmann made changes - 18/Jan/08 09:26 AM
The TestJavadocReport mojo has @phase generate-test-sources which doesn't make much sense either. I bet the original committer meant @execute phase=generate-test-sources instead. fixed in r661899, snapshot deployed
Vincent Siveton made changes - 30/May/08 05:20 PM
Vincent Siveton made changes - 30/May/08 05:20 PM
Vincent Siveton made changes - 30/May/08 05:25 PM
Benjamin Bentmann made changes - 30/May/08 05:50 PM
Vincent Siveton made changes - 05/Jun/08 07:22 AM
Benjamin Bentmann made changes - 02/Jan/09 05:18 AM
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Major
Regression: 2.4-SNAPSHOT does not generate docs for generates sources if run outside a build
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.