maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Closed] (MSHARED-590) add plugin name to report identification in forked execution messages
Date Sat, 10 Sep 2016 17:04:20 GMT

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

Hervé Boutemy closed MSHARED-590.
---------------------------------
    Resolution: Fixed

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

Mime
View raw message