[MNG-3387] Enforce redeployment for deploy phase

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0
• Component/s: Deployment
• Assignee: Brett Porter
• Reporter: Martin Buechler
• Created: 06/Feb/08 13:08
• Updated: 18/Jun/08 12:20
• Resolved: 18/Jun/08 12:20

Description

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.

Issue Links

• duplicates: MNG-4377 The deployer should detect previous deployments of the same version and die if that's the case.