[
https://jira.codehaus.org/browse/MJAVADOC-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279496#comment-279496
]
Chris Wilton commented on MJAVADOC-311:
---------------------------------------
I can confirm this behaviour.
If I add the javadoc plugin configuration to the {{<reporting>}} section of the
_parent_ pom, then the aggregated javadocs are created when {{mvn site}} is run
at the parent level. But they are linked to the _parent_ project and we don't
want them there, we want them in the _library_ module's project reports.
If the javadoc configuration is instead added to the {{<reporting>}} section of
the _library_ pom, then the aggregated javadocs are not created at all if {{mvn
site}} is run at the _parent_ level. They are created only if I run {{mvn
site}} at the _library_ level.
Currently, as a workaround in my project, I am running {{mvn site}} at both the
_parent_ and the _library_ level, one after the other. But that does not play
nicely with Hudson/Jenkins scheduled site builds - I get wrong URL links and
breadcrumbs in the library module. So I have to create and deploy the site
manually.
> Aggregated javadoc report not generated for multi-module project at sub-level
> if run from parent level.
> -------------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-311
> URL: https://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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
