[ https://jira.codehaus.org/browse/MDEPLOY-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MDEPLOY-141. ---------------------------------- Resolution: Cannot Reproduce Assignee: Robert Scholte Upgrading to a more recent version of Maven seems to be the solution. > Deploy fails for releases with repository deployment policy set to Disable > Redeploy > ----------------------------------------------------------------------------------- > > Key: MDEPLOY-141 > URL: https://jira.codehaus.org/browse/MDEPLOY-141 > Project: Maven Deploy Plugin > Issue Type: Bug > Affects Versions: 2.7 > Reporter: Manfred Schürhoff > Assignee: Robert Scholte > Priority: Minor > > We recently switched from Archiva to Nexus. The deployment policy for the > release repository in Nexus is set to Disable Redeploy. However, this now > causes problems that are described in MDEPLOY-134 and MDEPLOY-137: when an > artifact is uploaded, it first uploads the pom and the artifact which works > OK, but then it tries to upload the sources of the artifact (also fine) and > again the pom which fails with HTTP 400: > {noformat}Error deploying artifact: Failed to transfer file: > http://nl-nexus/nexus/content/repositories/releases/<groupId>.<artifactId>.<version>.pom. > Return code is: 400{noformat} > We were still using version 2.3 of the maven-deploy-plugin, but we switched > to the latest 2.7 version hoping this would solve the issues described in > MDEPLOY-134 and MDEPLOY-137, but the problem still remains. We've also tried > setting uniqueVersion to false for the releases in distributionManagment, but > that also doesn't help (and is something we'd rather not do). -- This message was sent by Atlassian JIRA (v6.1.6#6162)