javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when 
aggregating a javadoc for a project
---------------------------------------------------------------------------------------------------------------

                 Key: MJAVADOC-194
                 URL: http://jira.codehaus.org/browse/MJAVADOC-194
             Project: Maven 2.x Javadoc Plugin
          Issue Type: Bug
    Affects Versions: 2.4
         Environment: Maven version: 2.0.9
Java version: 1.5.0_12
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
            Reporter: Lois Modesitt
         Attachments: m209out-UsingJavadoc2.3.txt, m209out-UsingJavadoc2.4.txt

The javadoc does not include the "additional source" files defined using the 
"build-helper:add-source" in each of my subproject pom files when using javadoc 
plugin 2.4.  The javadoc plugin 2.3 worked correctly.

I use the "build-helper:add-source" to include additional source directories to 
the build.  The additional source directories contain my generated source file. 
 When I run the command using javadoc plugin version 2.4:
mvn javadoc:javadoc -Daggregate=true
(or have the aggregate=true specified inside of the pom) the 
"build-helper:add-source" is not run for each of the subprojects before the 
aggregated javadoc is created.  Therefore the javadoc does not include the 
documentation for the files in the additional source directories.

I also noted that the output for 2.3 javadoc plugin is:
[INFO]    task-segment: [javadoc:javadoc] (aggregator-style)
but the output for the 2.4 javadoc plugin is:
[INFO]    task-segment: [javadoc:javadoc]

I am not sure if the above output is changed between versions or if the 
"aggregator-style" is not detectd in the 2.4 version and has an influence in 
this issue.

I have attached the log file for running my project using javadoc plugin 
version 2.3 and 2.4.  Version 2.3 works and version 2.4 does not include the 
additional source files in the aggregated javadoc.

-- 
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

        

Reply via email to