[
https://issues.apache.org/jira/browse/MNG-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5416.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Forked execution message should specify the forked goal
> -------------------------------------------------------
>
> Key: MNG-5416
> URL: https://issues.apache.org/jira/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
(v7.6.3#76005)
