[
http://jira.codehaus.org/browse/MJAVADOC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189755#action_189755
]
Jörg Hohwiller commented on MJAVADOC-245:
-----------------------------------------
Sorry for delay...
I tried your testcase and aggregated javadoc works with "mvn site" as well as
with "mvn site:stage".
However a Javadoc per module is not generated but is also not configured so not
a bug so far.
Next I try to figure out the differences to my project...
Maybe it is just because I also wanted to have javadocs per module.
See if I will find the time to extract a testcase to show the problem...
However my workaround works okay.
> Aggregate does not work
> -----------------------
>
> Key: MJAVADOC-245
> URL: http://jira.codehaus.org/browse/MJAVADOC-245
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.5, 2.6
> Reporter: Jörg Hohwiller
> Attachments: MJAVADOC-245.zip
>
>
> I want to have an aggregated javadoc for the entire project as well as per
> module.
> Therefore I followed instructions at:
> http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html
> When I do mvn site:stage I get no aggregated javadoc but just per module.
> This does not even change if I only do
> <reportSets>
> <reportSet>
> <reports>
> <report>aggregate</report>
> </reports>
> </reportSet>
> </reportSets>
> So to me this looks as if <reportSets> is magically ignored here.
> I have tested 2.5 as well as 2.6 from
> https://repository.apache.org/content/repositories/maven-staging-027/org/apache/maven/plugins/maven-javadoc-plugin/2.6/
--
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
