[
https://issues.apache.org/jira/browse/MJAVADOC-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957489#comment-17957489
]
Olivier Lamy commented on MJAVADOC-66:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#471|https://github.com/apache/maven-javadoc-plugin/issues/471].
> Aggregated Javadoc does not use module-level dependencies
> ---------------------------------------------------------
>
> Key: MJAVADOC-66
> URL: https://issues.apache.org/jira/browse/MJAVADOC-66
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: WinXP, Maven 2.0.4, maven-javadoc-plugin from source
> Reporter: Wendy Smoak
> Assignee: Jesse Stockall
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
