You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benson Margulies (JIRA)" <ji...@codehaus.org> on 2015/02/02 13:55:20 UTC
[jira] (MNG-5416) Forked execution message should specify the
forked goal
[ https://jira.codehaus.org/browse/MNG-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies reassigned MNG-5416:
-------------------------------------
Assignee: (was: Benson Margulies)
> Forked execution message should specify the forked goal
> -------------------------------------------------------
>
> Key: MNG-5416
> URL: https://jira.codehaus.org/browse/MNG-5416
> Project: Maven
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 3.0.4
> Reporter: Benson Margulies
> Priority: Minor
>
> {noformat}
> [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> [INFO] Forking License Test :: global-db - something to depend on 1
> [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> {noformat}
> One of the struggles in debugging a build can be forked executions.
> If the forked execution implicitly depends on some goal of some plugin that is bound to a phase after the forked goal, the build fails. This would be easier to debug if this message included the goal.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)