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 2008/06/13 02:40:12 UTC

[jira] Updated: (MNG-3387) Enforce redeployment for deploy phase

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

Brett Porter updated MNG-3387:
------------------------------

    Fix Version/s: 2.1-alpha-1

> Enforce redeployment for deploy phase
> -------------------------------------
>
>                 Key: MNG-3387
>                 URL: http://jira.codehaus.org/browse/MNG-3387
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 2.1
>            Reporter: Martin Buechler
>             Fix For: 2.1-alpha-1
>
>
> Is there a possibility to enforce the redeployment of an artefact during the
> build? I get the message 'The artifact xxx has already been deployed. Not
> deploying again.'
> Yes, it exists but I want to replace it. 
> There is difference in behaviour of the m2eclipse plugin to the current cli versions 2.0.x.
> see http://www.nabble.com/Enforce-redeployment-during-Build-td14997988s177.html
> Brian E Fox said there:
> This was added to 2.1, it won't happen in 2.0.x. A flag to force it
> needs to be added to the interface and to the deploy plugin, and it
> should be backported to 2.0. Can you write a jira?
> Done.

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