[jira] Updated: (MNG-3450) build planning may fail to find forked executions on late-bound plugins

["Jason van Zyl (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-3450:
-------------------------------

    Fix Version/s:     (was: 2.1-alpha-1)
                   2.1-alpha-2

> build planning may fail to find forked executions on late-bound plugins
> -----------------------------------------------------------------------
>
>                 Key: MNG-3450
>                 URL: http://jira.codehaus.org/browse/MNG-3450
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.1-alpha-1
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.1-alpha-2
>
>
> When a plugin cannot be located during the build-planning part of the build (which happens before any of the plugins execute), that plugin's resolution is deferred until the first time it's run in the build. Right before the plugin is scheduled to run, a special internal state-management mojo is executed to retry plugin resolution. If that fails, the build fails.
> However, we need to be sure that plugins that are late-bound in this way and that specify forked executions of one type or another have their forked executions included in the build. This would be the first case of a mojo modifying the build plan in which it is executing (to inject a forked execution ahead of the next mojo to run, which is the one that was late-bound).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira