[MDEPLOY-74] Add an option to be able to abort if an artifact is already present in the deployment repository

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Not A Problem
• Labels: scrub-review-started
• Assignee: Robert Scholte
• Reporter: Baptiste MATHUS
• Created: 27/Mar/08 11:23
• Updated: 03/Jan/15 09:34
• Resolved: 03/Jan/15 09:34

Description

Hi all,

Would be great if it was possible to use a command like:
mvn deploy -DfailIfPresent=true (false by default, to behave as currently)

That switch would do a build failure if the artifact is found in the deployment repository.

Alternatively or in addition, a -DdryRun=true could add a simulation mode to this plugin. Particularly, it would clearly display if the artifact would be overriding an already present one or not.

Cheers.

Issue Links

• depends upon: MNG-4377 The deployer should detect previous deployments of the same version and die if that's the case.
• is duplicated by: MDEPLOY-34 Option to set deployed artifact read-only should be added.
• relates to: MRM-747 Archiva should prevent re-deployment of released or non-snapshot versioned artifacts
• relates to: MRM-992 Managed Repository: allow to block deployment of existing release-artifacts
• relates to: MNG-4377 The deployer should detect previous deployments of the same version and die if that's the case.