[
http://jira.codehaus.org/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184119#action_184119
]
Martin Desruisseaux commented on MJAVADOC-134:
----------------------------------------------
Actually I'm interrested in a variant of this request, where the javadoc is
aggregated only starting from the submodule which ask for it. Such feature
could (maybe) help to workaround MJAVADOC-145 (closed, but the issue reported
in that task still occurs in my project and I have not yet found a workaround),
if we can avoid the aggregation of javadoc for Maven plugins.
> Support aggregated reports at each level in the multi-module hierarchy
> ----------------------------------------------------------------------
>
> Key: MJAVADOC-134
> URL: http://jira.codehaus.org/browse/MJAVADOC-134
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
> Affects Versions: 2.2
> Reporter: John Allen
>
> The current system makes the assumption that if one wants aggregated reports
> one does not want further javadoc reports (aggregated ones) down the
> hierarchy. We do require this functionality and in fact do the same for all
> our reports (PMD, Checkstyle, Clover, JXR, Surefire, etc):
> A->B->C->D1 (JAR)
> A->B->C->D2 (JAR)
> A->B->E(JAR)
> A->F (JAR)
> A - javadoc for D1,D2,E,F
> B - javadoc for D1,D2,E
> C - javadoc for D1,D2
> D1 - javadoc for D1
> D2 - javadoc for D2
> E - javadoc for E
> F - javadoc for F
> This way there is the required info at the appropriate level throughout the
> hierarchy. And nope we dont care about space or generation times:)
--
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
