[ http://jira.codehaus.org/browse/MDEPLOY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128893#action_128893 ]
Baptiste MATHUS commented on MDEPLOY-74: ---------------------------------------- bq. +1 for regular releases, -1 for snapshots Well, this is only a problem with -DuniqueVersion=false I guess. Since default behaviour will generate a timestamp suffix, so that wouldn't override existing artifact. But IMO, this isn't a real problem since SNAPSHOT are unstable by definition, so maybe overriding it should be monitored at all. Maybe an additional option for the additional option could be added to handle this, like -DalsoForSnapshots :-). > 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
