[jira] [Commented] (MJAVADOC-311) Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.

["Anton Vinogradov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MJAVADOC-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071639#comment-15071639 ] 

Anton Vinogradov commented on MJAVADOC-311:
-------------------------------------------

Hi, 
Is there any chances to solve the issue?

> Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-311
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-311
>             Project: Maven Javadoc Plugin
>          Issue Type: Wish
>    Affects Versions: 2.7
>         Environment: Windows Vista x64, JDK 6u22, Maven 3.0
>            Reporter: André Fügenschuh
>         Attachments: maven3-site-javadoc-testcase.zip
>
>
> With a +multi-module project design+ (cf. attached testcase):
> {noformat}
> - parent        (pom)
>   + library     (pom)  // javadoc:aggregate
>     + module-a  (jar)
>     + module-b  (jar)
>   + application (jar)  // javadoc:javadoc
> {noformat}
> run
> {{mvn site}} | {{mvn -DstagingDirectory=\[dir\] site:stage}}
> at _parent_ level.
> +Result:+
> Aggregated javadocs for _library_ are *not* generated (but are properly done if {{mvn site}} is run at _library_ level itself), while javadocs at _application_ level are generated.
> OT: as appropriate {{<modules>}} sections are declared (cf. attached testcase), {{mvn compile}} runs as expected at _parent_ level.
> This is a follow-up to MJAVADOC-181, which, although marked as resolved, has never been working for me using the _old_ site/reports configuration for Maven 2.2.1 / Site plugin 2.1.1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)