[jira] Commented: (MJAVADOC-66) Aggregated Javadoc does not use module-level dependencies

2006-09-29 Thread Martin Desruisseaux (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-66?page=comments#action_76148 ] 

Martin Desruisseaux commented on MJAVADOC-66:
-

Is this bug really fixed in {{maven-javadoc-plugin}} version 2.0? Aggregated 
javadoc still fail to find module-level dependencies when building the Geotools 
project for example.

 Aggregated Javadoc does not use module-level dependencies
 -

 Key: MJAVADOC-66
 URL: http://jira.codehaus.org/browse/MJAVADOC-66
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.0
 Environment: WinXP, Maven 2.0.4, maven-javadoc-plugin from source
Reporter: Wendy Smoak
 Assigned To: Jesse McConnell
 Fix For: 2.0

 Attachments: mjavadoc66.patch


 The 'mvn javadoc:javadoc' command works fine with the latest plugin built 
 from source and this in struts/action/trunk/pom.xml:
 reporting
 plugins
plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
 /plugin
  /plugins
/reporting
 It drops into each module and builds the javadoc there.  However, if I add 
 configuration and try to get aggregated Javadoc at the top level:
   configuration
 aggregatetrue/aggregate
   /configuration
 It seems to build the aggregated Javadoc okay, but then when starts 
 descending into each module it fails complaining Cannot find
 symbol... about things like commons-logging and the Servlet api. These are 
 declared as dependencies at the module level.

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




[jira] Commented: (MJAVADOC-66) Aggregated Javadoc does not use module-level dependencies

2006-04-27 Thread Jesse McConnell (JIRA)
[ http://jira.codehaus.org/browse/MJAVADOC-66?page=comments#action_64322 ] 

Jesse McConnell commented on MJAVADOC-66:
-

issue here is that the aggregate option will force javadoc generation to only 
occur at the top lvl execution root of the project, and it does this by putting 
adding all of the source roots of the reactor projects into the list of source 
paths to process.  However the dependencies of the subjects are not added into 
the mix so those symbols will indeed not be found.

one potential approach to this would be walk through the dependencies of the 
subprojects and add those into the classpath of the report, but that probably 
will break on windows since there is a max length of the commandline and this 
plugin builds out a plexus commandline object which would have huge potential 
if this were a larger project using the aggregate.

another might be to get this plugin to not be using the commandline?  have to 
look into it I suppose

 Aggregated Javadoc does not use module-level dependencies
 -

  Key: MJAVADOC-66
  URL: http://jira.codehaus.org/browse/MJAVADOC-66
  Project: Maven 2.x Javadoc Plugin
 Type: Bug

 Versions: 2.0
  Environment: WinXP, Maven 2.0.4, maven-javadoc-plugin from source
 Reporter: Wendy Smoak
  Fix For: 2.0



 The 'mvn javadoc:javadoc' command works fine with the latest plugin built 
 from source and this in struts/action/trunk/pom.xml:
 reporting
 plugins
plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
 /plugin
  /plugins
/reporting
 It drops into each module and builds the javadoc there.  However, if I add 
 configuration and try to get aggregated Javadoc at the top level:
   configuration
 aggregatetrue/aggregate
   /configuration
 It seems to build the aggregated Javadoc okay, but then when starts 
 descending into each module it fails complaining Cannot find
 symbol... about things like commons-logging and the Servlet api. These are 
 declared as dependencies at the module level.

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