maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <j...@codehaus.org>
Subject [jira] (MSHARED-266) run aggregator reports only when current projet is pom packaging and has modules
Date Sun, 11 May 2014 14:30:10 GMT

     [ https://jira.codehaus.org/browse/MSHARED-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Herve Boutemy closed MSHARED-266.
---------------------------------

       Resolution: Fixed
    Fix Version/s: maven-reporting-exec-1.2
         Assignee: Herve Boutemy

fixed in [r1593762|http://svn.apache.org/r1593762]

the solution is not exactly what was expected when creating the issue: in fact, *lifecycle
was always forked* and report was executed only when canGenerateReport() was true

now lifecycle will be forked only when canGenerateReport() is true: this will reduce the count
of forked lifecycles, the key algorithm will be in canGenerateReport() method in every reporting
plugin/mojo

> 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)

Mime
View raw message