[jira] [Commented] (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy
[
https://issues.apache.org/jira/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827253#comment-16827253
]
Falko Modler commented on MJAVADOC-134:
---
For those looking for a solution to retain the original bahaviour when using
{{}} (instead of {{reporting}}): Have a look at MJAVADOC-602.
> Support aggregated reports at each level in the multi-module hierarchy
> --
>
> Key: MJAVADOC-134
> URL: https://issues.apache.org/jira/browse/MJAVADOC-134
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.2
>Reporter: skaze
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: MJAVADOC-134_multiaggregate.zip
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy
[ https://issues.apache.org/jira/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724531#comment-16724531 ] Hudson commented on MJAVADOC-134: - Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » master #95 See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/95/ > Support aggregated reports at each level in the multi-module hierarchy > -- > > Key: MJAVADOC-134 > URL: https://issues.apache.org/jira/browse/MJAVADOC-134 > Project: Maven Javadoc Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: skaze >Assignee: Robert Scholte >Priority: Major > Fix For: 3.0.2 > > Attachments: MJAVADOC-134_multiaggregate.zip > > > 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 was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy
[ https://issues.apache.org/jira/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724504#comment-16724504 ] Hudson commented on MJAVADOC-134: - Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-134 #2 See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-134/2/ > Support aggregated reports at each level in the multi-module hierarchy > -- > > Key: MJAVADOC-134 > URL: https://issues.apache.org/jira/browse/MJAVADOC-134 > Project: Maven Javadoc Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: skaze >Priority: Major > Attachments: MJAVADOC-134_multiaggregate.zip > > > 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 was sent by Atlassian JIRA (v7.6.3#76005)
[jira] Commented: (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy
[ http://jira.codehaus.org/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=190853#action_190853 ] Vincent Siveton commented on MJAVADOC-134: -- Martin, FYI MJAVADOC-257 should fix your problem 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
[jira] Commented: (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy
[ http://jira.codehaus.org/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
