title: Strategy for maven deploy via a Jenkins job
body: <p>I have a Jenkins job that use maven build goals 'clean package deploy' for the master git branch.  However, due to the nexus repo not allowing redeploys, if the Jenkins job runs a second time without the version changing, it will fail with the expected 400 Bad Request error:</p>
  
  <pre><code>org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
      org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) 
      on project common-library: 
  Failed to deploy artifacts: Could not transfer artifact 
      net.bacon.common:common-library:pom:1.2.13 from/to bacon-releases 
      (https://maven.bacon.com/nexus/content/repositories/releases): 
  Failed to transfer file: 
      https://maven.bacon.com/nexus/content/repositories/releases/net/bacon/common/common-library/1.2.13/common-library-1.2.13.pom. 
  Return code is: 400, ReasonPhrase:Bad Request.
  </code></pre>
  
  <p>Can anyone suggest a different strategy, whereby the deploy goal can run without making the Jenkins job fail?</p>