maven部署&x2B；nexus因请求错误而失败

我在构建过程中遇到一些问题

构建完成得很好，Jenkins开始将文件上传到nexus。一切都很好，但后来由于某种原因失败了，最奇怪的是，提到的没有上传的文件实际上已经上传了，我可以在nexus中找到它

以下是输出：

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] pn-parent
[INFO] pn-domain
[INFO] pn-infra
[INFO] pn-config
[INFO] datalink-repository
[INFO] pn-service
[INFO] pn-backend
[INFO] 
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building pn-parent 0.0.707
[INFO] ------------------------------------------------------------------------
[WARNING] The artifact junit:junit-dep:pom:4.11 has been relocated to junit:junit:pom:4.11
[INFO] 
[INFO] --- maven-jar-plugin:2.5:jar (default-cli) @ pn-parent ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /var/lib/jenkins/jobs/webapps-server-side-release/workspace/pn-parent/target/pn-parent-0.0.707.jar
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy (default-cli) @ pn-parent ---
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-parent/0.0.707/pn-parent-0.0.707.pom          
     Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-parent/0.0.707/pn-parent-0.0.707.pom (15 KB at 111.6 KB/sec)
Downloading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-parent/maven-metadata.xml
     Downloaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-parent/maven-metadata.xml (21 KB at 1036.9 KB/sec)
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-parent/maven-metadata.xml
     Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-parent/maven-metadata.xml (21 KB at 864.7 KB/sec)
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building pn-domain 0.0.707
[INFO] ------------------------------------------------------------------------
[WARNING] The artifact junit:junit-dep:pom:4.11 has been relocated to junit:junit:pom:4.11
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-cli) @ pn-domain ---
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy (default-cli) @ pn-domain ---
      Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-domain/0.0.707/pn-domain-0.0.707.jar    
      Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/datalink-repository/0.0.707/datalink-repository-0.0.707.jar (624 KB at 7606.1 KB/sec)
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/datalink-repository/0.0.707/datalink-repository-0.0.707.pom
2/4 KB       
4/4 KB   
      Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/datalink-repository/0.0.707/datalink-repository-0.0.707.pom (4 KB at 93.0 KB/sec)
Downloading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/datalink-repository/maven-metadata.xml
       Downloaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/datalink-repository/maven-metadata.xml (21 KB at 1382.8 KB/sec)
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/datalink-repository/maven-metadata.xml
       Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/datalink-repository/maven-metadata.xml (21 KB at 1037.8 KB/sec)
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building pn-service 0.0.707
[INFO] ------------------------------------------------------------------------
[WARNING] The artifact junit:junit-dep:pom:4.11 has been relocated to junit:junit:pom:4.11
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-cli) @ pn-service ---
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy (default-cli) @ pn-service ---
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn-service/0.0.707/pn-service-0.0.707.jar     
       Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/0.0.707/pn-backend-0.0.707.war (1247 KB at 19480.3 KB/sec)
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/0.0.707/pn-backend-0.0.707.pom      
       Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/0.0.707/pn-backend-0.0.707.pom (11 KB at 376.2 KB/sec)
Downloading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/maven-metadata.xml  
        Downloaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/maven-metadata.xml (21 KB at 1213.1 KB/sec)
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/maven-metadata.xml  
       Uploaded: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/maven-metadata.xml (21 KB at 1031.7 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] pn-parent ................................... SUCCESS [  1.081 s]
[INFO] pn-domain ................................... SUCCESS [  0.696 s]
[INFO] pn-infra .................................... SUCCESS [  0.295 s]
[INFO] pn-config ................................... SUCCESS [  0.275 s]
[INFO] datalink-repository ............................... SUCCESS [  0.390 s]
[INFO] pn-service .................................. SUCCESS [  0.475 s]
[INFO] pn-backend .................................. SUCCESS [  1.043 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.234 s
[INFO] Finished at: 2014-07-17T14:31:30+00:00
[INFO] Final Memory: 19M/206M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "release" could not be activated because it does not exist.
using global settings config with name mycompany-global-dev-maven-settings
[workspace] $ /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.1.1/bin/mvn -gs /tmp/global-settings8833627416958413984.xml deploy:deploy-file -Durl=http://maven.mycompany.com:8081/nexus/content/repositories/releases/ -DrepositoryId=mycompany.repository -DpomFile=pn-parent/Backend/pom.xml -Dfile=pn-parent/Backend/target/pn-backend.war
[WARNING] 
[WARNING] Some problems were encountered while building the effective settings
[WARNING] 'usePluginRegistry' is deprecated and has no effect. @ /var/lib/jenkins/.m2/settings.xml
[WARNING] 
[INFO] Scanning for projects...
[INFO] 
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-deploy-plugin:2.7:deploy-file (default-cli) @ standalone-pom ---
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/0.0.707/pn-backend-0.0.707.war
...
Uploading: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/0.0.707/pn-backend-0.0.707.pom
2/11 KB          
4/11 KB   
6/11 KB   
8/11 KB   
10/11 KB   
11/11 KB   

       [INFO] ------------------------------------------------------------------------
       [INFO] BUILD FAILURE
       [INFO] ------------------------------------------------------------------------
       [INFO] Total time: 1.928 s
       [INFO] Finished at: 2014-07-17T14:31:33+00:00
       [INFO] Final Memory: 6M/142M
       [INFO] ------------------------------------------------------------------------
       [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on project standalone-pom: Failed to deploy artifacts: Could not transfer artifact com.mycompany.pn:pn-backend:war:0.0.707 from/to mycompany.repository (http://maven.mycompany.com:8081/nexus/content/repositories/releases/): Failed to transfer file: http://maven.mycompany.com:8081/nexus/content/repositories/releases/com/mycompany/pn/pn-backend/0.0.707/pn-backend-0.0.707.war. Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
         [ERROR] 
         [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
         [ERROR] Re-run Maven using the -X switch to enable full debug logging.
          [ERROR] 
          [ERROR] For more information about the errors and possible solutions, please read the following articles:
         [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
         Build step 'Conditional steps (multiple)' marked build as failure
         [locks-and-latches] Releasing all the locks
         [locks-and-latches] All the locks released
         [Current build status] check if current [FAILURE] is worse or equals then [SUCCESS] and better or equals then [SUCCESS]
         Run condition [Current build status] preventing perform for step [Record JaCoCo coverage report]
        Description set: 
        Start to submit Nexus scheduled tasks.
        Submitting... [id: 36, name: release-build, type: Rebuild Maven Metadata Files]
        End to submit Nexus scheduled tasks successfully.
         Notifying upstream projects of job completion
        Finished: FAILURE

---

我的一位同事也遇到了同样的问题，maven试图两次上传工件。 我们在论坛中找到了一些帮助，链接如下。 他的回答对我们起了作用：

尝试运行mvn-PreRelease配置文件帮助：有效的pom。你会发现 maven源插件有两个执行部分

[……]

要解决此问题，请查找您使用过的所有位置 maven源插件，并确保使用“id” 附加源，使其与发布配置文件相同。然后 这些部分将合并。最佳实践是这样的 一致性您需要在项目的根pom中配置此一致性 在build>pluginManagement中，而不是在您的孩子poms中。在孩子身上 pom您只需在build>插件中指定要使用的插件 maven源插件，但您不提供执行

---

我也遇到了这个问题。在我的例子中，我将Nexus存储库策略配置为接受发布人工制品，但实际上我正在将快照人工制品推送到repo。因为我想要快照回购，我只是简单地改变了政策，一切都很好。

这也发生在我身上。在我的例子中，我部署了一个发布版本。要修复此问题，请确保Nexus中还不存在版本号。如果是多模块项目，还应检查子模块的版本。

快照和发布冲突也会导致400个错误请求。您尝试更新的项目可能是pom中的快照：

<version>0.0.1-SNAPSHOT</version>

0.0.1-SNAPSHOT

而settings.xml中的存储库拒绝快照。解决方案：

<version>0.0.1</version>

0.0.1

---

反过来也会发生这种情况：尝试将发行版（

版本

没有快照）版本部署到快照存储库。

您解决过这个问题吗？我也有同样的问题。我想也许maven试图上传工件两次，但我不确定为什么或者如何停止（我的存储库中禁用了重新部署，这是应该的）。@AlienBishop同样的问题，在我的例子中是由于两个不同的maven插件，maven源插件和maven汇编插件。查看此问题以修复maven程序集插件error@AlienBishop对于maven源插件错误，请参见这里的答案。在我的例子中，我必须进行两次修复，因为maven deploy插件已经负责上传工件。请在答案正文中包含链接中的所有相关信息。当链接腐烂/移动/消亡或变得不可用时，仅链接的答案往往会失去价值。答案已编辑。谢谢你的反馈，埃维特和皇家空军。