[
https://jira.codehaus.org/browse/MSHARED-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346647#comment-346647
]
Herve Boutemy commented on MSHARED-266:
---------------------------------------
the change makes maven-site-plugin "full-reporting" IT fail, because [cobertura
report|http://mojo.codehaus.org/cobertura-maven-plugin/cobertura-mojo.html]
isn't generated
looking at build.log:
{noformat}[INFO] Not executing cobertura:report as the cobertura data file
(/home/herve/projets/maven/trunks/plugins/maven-site-plugin/target/it/full-reporting/target/cobertura/cobertura.ser)
could not be found{noformat}
in the case of cobertura, the lifecycle forking requires to be executed before
testing canGenerateReport() since the forked execution result affects the result
this is not the same expectations than m-javadoc-p
I fear I need to revert... :(
> 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)
