[ http://jira.codehaus.org/browse/MJAVADOC-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl moved MSITE-518 to MJAVADOC-311: ---------------------------------------------- Component/s: (was: multi module) (was: inheritance) Affects Version/s: (was: 3.0-beta-3) 2.7 Key: MJAVADOC-311 (was: MSITE-518) Project: Maven 2.x Javadoc Plugin (was: Maven 2.x and 3.x Site Plugin) > Aggregated javadoc report not generated for multi-module project at sub-level > if run from parent level. > ------------------------------------------------------------------------------------------------------- > > Key: MJAVADOC-311 > URL: http://jira.codehaus.org/browse/MJAVADOC-311 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug > 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 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