[
https://issues.apache.org/jira/browse/MSHARED-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15480035#comment-15480035
]
Hudson commented on MSHARED-590:
--------------------------------
SUCCESS: Integrated in Jenkins build maven-shared #2882 (See
[https://builds.apache.org/job/maven-shared/2882/])
[MSHARED-590] prepended report goal by plugin artifactid (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1760185])
* (edit)
maven-reporting-exec/src/main/java/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.java
> add plugin name to report identification in forked execution messages
> ---------------------------------------------------------------------
>
> Key: MSHARED-590
> URL: https://issues.apache.org/jira/browse/MSHARED-590
> 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
>
>
> sometimes, report of a plugin is named "report" (sic!), then we get
> {noformat}[INFO] configuring report plugin
> org.apache.maven.plugins:maven-plugin-plugin:3.4
> [INFO] preparing 'report' report requires 'process-classes' forked phase
> execution
> ...
> [INFO] 'process-classes' forked phase execution for 'report' report
> preparation done{noformat}
> not really easy to understand
> Since a report is a goal of a plugin, instread of "report", we could prepend
> with the plugin name: "maven-plugin-plugin:report"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
