You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2008/03/22 19:39:45 UTC
[jira] Moved: (MJAVADOC-181) Javadoc report not generated for
multi-module project if run from parent level.
[ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg moved MSITE-309 to MJAVADOC-181:
------------------------------------------------
Affects Version/s: (was: 2.0-beta-6)
Component/s: (was: multi module)
Key: MJAVADOC-181 (was: MSITE-309)
Project: Maven 2.x Javadoc Plugin (was: Maven 2.x Site Plugin)
> Javadoc report not generated for multi-module project if run from parent level.
> -------------------------------------------------------------------------------
>
> Key: MJAVADOC-181
> URL: http://jira.codehaus.org/browse/MJAVADOC-181
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Environment: W2K, JDK 6u5, Maven 2.0.8
> Reporter: André Fügenschuh
> Attachments: maven-site-javadoc-testcase.zip
>
>
> For the following project design (s. attached testcase):
> parent
> \- library // javadoc:aggregate!
> \- module-a
> \- module-b
> \- application
> javadoc report for 'library' is *not* generated (not invoked), if 'mvn site' is
> called at 'parent' level (but is properly done if run at 'library' level itself).
--
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