[
https://jira.codehaus.org/browse/MSHARED-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346658#comment-346658
]
Herve Boutemy edited comment on MSHARED-266 at 5/18/14 3:27 AM:
----------------------------------------------------------------
change reverted and replaced by initial idea in
[r1595568|http://svn.apache.org/r1595568], ie for reports automatically added
(only plugin is specified but not reports), don't add aggregator reports if not
at execution root and in an aggregator pom
notice that this affects a little bit results for MJAVADOC-711:
generate-sources phase is executed a little more, but at least, this doesn't
break existing plugins
was (Author: hboutemy):
change reverted and replaced by initial idea in
[r1595568|http://svn.apache.org/r1595568], ie for reports automatically added
(only plugin is specified but not reports), don't add aggregator reports if not
at execution root and in an aggregator pom
> run aggregator reports only when current projet is pom packaging and has
> modules
> --------------------------------------------------------------------------------
>
> Key: MSHARED-266
> URL: https://jira.codehaus.org/browse/MSHARED-266
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-reporting-exec
> Affects Versions: maven-reporting-exec-1.0.2
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Fix For: maven-reporting-exec-1.2
>
>
> would fix MSITE-454
> simply adding a plugin to reporting section, without defining any reportSets,
> will avoid running aggregate reports in every module
> notice: this will work only with Maven 3, since Maven 2 runs reports from
> core and not from m-site-p/m-reporting-exec
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
