[jira] Updated: (MJAVADOC-181) Javadoc report not generated for multi-module project if run from parent level.

["Stevo Slavic (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MJAVADOC-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stevo Slavic updated MJAVADOC-181:
----------------------------------

    Attachment: maven_release_failure_caused_by_mjavadoc.txt

I think I just got hit by this issue - release:perform fails on multi-module project because of javadoc plugin. See [^maven_release_failure_caused_by_mjavadoc.txt] for relevant build output.

> 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, maven_release_failure_caused_by_mjavadoc.txt, 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