[
http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250443#action_250443
]
Herve Boutemy commented on MJAVADOC-181:
----------------------------------------
I don't understand: the IT generates apidocs in module-a and module-b but not
in library
IIUC, the expected result was the contrary, no?
can someone confirm that the actual result with maven-javadoc-plugin 2.6 and
2.7 is really what was expected?
(FYI, I'm running into trouble with MJAVADOC-286, where the fix breaks the
actual behaviour, and the more I think at it, the more I'm convinced this issue
IT checks the contrary to the expected result...)
> 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
> Assignee: Vincent Siveton
> Fix For: 2.6
>
> Attachments: maven-site-javadoc-testcase.zip, MJAVADOC-181-1.patch,
> MJAVADOC-181.patch
>
>
> 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
