[ http://jira.codehaus.org/browse/MDEPLOY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129123#action_129123 ]
Baptiste MATHUS commented on MDEPLOY-74: ---------------------------------------- Well, according to Brian E. Fox, this behaviour is already the default in the "new code" (maven 2.1), cf. http://www.nabble.com/-deploy-plugin--Abort-deploy-when-a-target-is-present-to16329568s177.html#a16353467 So, I guess the "fix version" of this bug report could be updated to show it's been fixed, isn't? > Add an option to be able to abort if an artifact is already present in the > deployment repository > ------------------------------------------------------------------------------------------------ > > Key: MDEPLOY-74 > URL: http://jira.codehaus.org/browse/MDEPLOY-74 > Project: Maven 2.x Deploy Plugin > Issue Type: Improvement > Reporter: Baptiste MATHUS > Priority: Minor > > 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 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
