You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2015/01/03 16:35:10 UTC
[jira] (MDEPLOY-74) Add an option to be able to abort if an
artifact is already present in the deployment repository
[ https://jira.codehaus.org/browse/MDEPLOY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MDEPLOY-74.
---------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
To be precise: it is not a bug of the maven-deploy-plugin. The fix has already been done in Maven Core.
> Add an option to be able to abort if an artifact is already present in the deployment repository
> ------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-74
> URL: https://jira.codehaus.org/browse/MDEPLOY-74
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Reporter: Baptiste MATHUS
> Assignee: Robert Scholte
> Priority: Minor
> Labels: scrub-review-started
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)