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

Hudson commented on MSHARED-589:
--------------------------------

SUCCESS: Integrated in Jenkins build maven-shared #2880 (See 
[https://builds.apache.org/job/maven-shared/2880/])
[MSHARED-589] improved after forked execution (hboutemy: 
[http://svn.apache.org/viewvc/?view=rev&rev=1760178])
* (edit) 
maven-reporting-exec/src/main/java/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.java
[MSHARED-589] added a message after forked execution to remember for which 
report preparation it was done (hboutemy: 
[http://svn.apache.org/viewvc/?view=rev&rev=1760172])
* (edit) 
maven-reporting-exec/src/main/java/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.java


> on forked execution, add explanations after execution
> -----------------------------------------------------
>
>                 Key: MSHARED-589
>                 URL: https://issues.apache.org/jira/browse/MSHARED-589
>             Project: Maven Shared Components
>          Issue Type: Improvement
>          Components: maven-reporting-exec
>    Affects Versions: maven-reporting-exec-1.2
>            Reporter: Hervé Boutemy
>            Assignee: Hervé Boutemy
>             Fix For: maven-reporting-exec-1.3
>
>
> currently, there is nothing displayed at the end of forked execution: it's 
> hard to remember that it was done for a report (and which one)
> adding a notice after the execution will improve understanding of what happens



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to