|
Benjamin Bentmann made changes - 30/May/08 05:50 PM
aggregated javadoc created BEFORE "build-helper:add-source" run on each module involved in the aggregated javadoc. Therefore the source files included with the "build-helper:add-source" is not included in the aggregated javadoc. Using the command: mvn javadoc:javadoc -Daggregate=true I used the 2.5-SNAPSHOT version of the maven-javadoc-plugin and this did not fix the problem. The attached log files show the order of execution of the "javadoc" and the "build-helper:add-source" for each module included in the project is different between 2.3 (works) and 2.4/2.5-SNAPSHOT (does not work).
Lois Modesitt made changes - 02/Jun/08 03:13 PM
Sorry, but I am not sure to understand correctly your usecase: could you send us a test case? UseCase: Problem: See the attached file JavaDocTestCase.zip.
Lois Modesitt made changes - 04/Jun/08 04:18 PM
Vincent Siveton made changes - 05/Jun/08 07:22 AM
Vincent Siveton made changes - 05/Jun/08 07:23 AM
It is mainly due to the remove of @aggregator tag
Vincent Siveton made changes - 05/Jun/08 07:25 AM
Having a mojo with @aggregator should resolve this issue Will this change be done to the 2.5-SNAPSHOT? If it is, will someone let me know so that I can try out the 2.5-SNAPSHOT with this fix? I just fixed I used the javadoc plugin 2.5-SNAPSHOT version: 20080606.132616-15 and the problem is still there. Is your change in this version of the SNAPSHOT? yes but you need to call javadoc:aggregate instead of javadoc:javadoc. See svn log file http://svn.apache.org/viewvc?rev=663917&view=rev Yes, that fix is great. I tried the test using javadoc:aggregate and the problem is resolved. Thanks Do you (Vincent) close this issue? Or am I supposed to do this? fixed due to
Vincent Siveton made changes - 06/Jun/08 02:40 PM
Benjamin Bentmann made changes - 02/Jan/09 05:18 AM
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This sound like a duplicate of
MJAVADOC-168which has just been fixed and a new snapshot deployed. Could you verify?