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

["Jesse McConnell (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MJAVADOC-66?page=all ]

Jesse McConnell updated MJAVADOC-66:
------------------------------------

    Attachment: mjavadoc66.patch

> 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
>     Assignee: 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>
>           <groupId>org.apache.maven.plugins</groupId>
>           <artifactId>maven-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>
>             <aggregate>true</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