[jira] [Comment Edited] (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy

["Falko Modler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827253#comment-16827253 ] 

Falko Modler edited comment on MJAVADOC-134 at 4/26/19 7:49 PM:
----------------------------------------------------------------

For those looking for a solution to retain the original bahaviour when using {{<build>}} (instead of {{<reporting>}}): Have a look at MJAVADOC-602.


was (Author: famod):
For those looking for a solution to retain the original bahaviour when using {{<build>}} (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)