maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Buechler (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MNG-3387) Enforce redeployment for deploy phase
Date Wed, 06 Feb 2008 19:09:28 GMT
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


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

        

Mime
View raw message