[
http://jira.codehaus.org/browse/MJAVADOC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186380#action_186380
]
Jörg Hohwiller commented on MJAVADOC-245:
-----------------------------------------
Jep I am sure that it does not work for my project when I call with "mvn site".
It works if I change to
<reportSets>
<reportSet>
<id>aggregate</id>
<configuration>
<aggregate>true</aggregate>
</configuration>
<reports>
<report>javadoc</report>
</reports>
</reportSet>
<reportSet>
<id>non-aggregate</id>
<configuration>
<aggregate>false</aggregate>
</configuration>
<reports>
<report>javadoc</report>
</reports>
</reportSet>
So at least I have a workaround. However "aggregate" property seems to be
deprecated and "aggregate" goal should be used instead.
> 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
