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

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/09/05 10:03:11 UTC

[jira] Updated: (MNG-1712) Maven should handle when a mojo doesn't requires a project

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

Brett Porter updated MNG-1712:
------------------------------

    Fix Version/s:     (was: 2.1)
                   2.x

> Maven should handle <extensions> when a mojo doesn't requires a project
> -----------------------------------------------------------------------
>
>                 Key: MNG-1712
>                 URL: http://jira.codehaus.org/browse/MNG-1712
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>            Reporter: Allan Ramirez
>             Fix For: 2.x
>
>
> I have encountered this when I am trying to create the deploy:deploy-file goal. 
> Currently, we can tell wagon what provider to use by adding  <extensions>, but  this mojo doesnt require a project so how can we tell the wagon what provider to use?

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