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 2013/01/01 14:49:13 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: Benson Margulies
> Forked execution message should specify the forked goal
> -------------------------------------------------------
>
> Key: MNG-5416
> URL: https://jira.codehaus.org/browse/MNG-5416
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 3.0.4
> Reporter: Benson Margulies
> Assignee: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira