You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2008/07/04 04:22:33 UTC

[jira] Updated: (MNG-3449) direct invocation of plugin after lifecycle calls that build it causes lifecycle-planning problem

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

Jason van Zyl updated MNG-3449:
-------------------------------

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

> direct invocation of plugin after lifecycle calls that build it causes lifecycle-planning problem
> -------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3449
>                 URL: http://jira.codehaus.org/browse/MNG-3449
>             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
>
>         Attachments: maven-find-local-repo-plugin.zip
>
>
> When you run a plugin build using something like:
> maven-foo-plugin$ mvn clean install foo:bar
> Maven fails to construct a build plan for this build, since it cannot resolve the prefix for the 'foo' plugin. We need to allow this to fail during build-planning, then do another late-bound approach to resolve the prefix and run the mojo. I'm attaching a test plugin for this.

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