你好,
artifactory插件在使用Maven release插件执行发布时导致构建失败。
在构建结束时，Artifactory尝试上传旧快照，而不是部署新快照。
这个问题已经在这里报道过了hap - 93并且在1.3.5版本中得到了修复，这似乎是一个回归。
人工用于检测发布构建并跳过上传阶段。
但是，发布版本在maven部署阶段被正确地上传到Artifactory。
下面是堆栈跟踪:
mojoSucceeded org.apache.maven.plugins:maven-release-plugin:2.3.2(default-cli) projectSucceeded ****:0.1.3-SNAPSHOT [INFO] Artifactory Build INFO Recorder:将工件部署到http://****/libs-release-local [INFO]部署工件:http://****/libs-snapshot-local/****/****-0.1.3-SNAPSHOT.pom mavenExecutionResult异常不空消息:内部错误:java.lang.RuntimeException:发布工件到Artifactory时发生错误:****\pom.xml。跳过剩余工件(如果有的话)和构建信息的部署。原因:发布工件到Artifactory: ****\pom.xml时发生错误。跳过剩余工件(如果有的话)和构建信息的部署。堆栈跟踪:org.apache.maven.InternalErrorException:内部错误:java.lang.RuntimeException:发布工件到Artifactory时发生错误:****\pom.xml。跳过剩余工件(如果有的话)和构建信息的部署。在org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.nativeemethodaccessorimpl . .invoke0(本机方法)sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java: 39) sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java: 25) java.lang.reflect.Method.invoke (Method.java: 597) org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard (Launcher.java: 329) org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java: 239) org.jvnet.hudson.maven3.agent.Maven3Main.launch (Maven3Main.java: 158)hudson. maven3builder .call(Maven3Builder.java:98) at hudson. maven3builder .call(Maven3Builder.java:64) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(futurettask .java:303) atjava.util.concurrent. futurettask .run(futurettask .java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.lang.Thread.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.RuntimeException:在发布工件到Artifactory: ****\pom.xml时发生错误。 Skipping deployment of remaining artifacts (if any) and build info. at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deployArtifacts(BuildDeploymentHelper.java:135) at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deploy(BuildDeploymentHelper.java:78) at org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded(BuildInfoRecorder.java:130) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:170) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 19 more Caused by: java.io.IOException: Failed to deploy file: HTTP response code: 409. HTTP response message: The target deployment path '****-0.1.3-20130123.161654-2.pom' does not match the POM's expected path prefix '****/0.1.4-SNAPSHOT'. Please verify your POM content for correctness and make sure the source path is a valid Maven repository root path. at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:642) at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:517) at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:292) at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deployArtifacts(BuildDeploymentHelper.java:133) ... 26 more channel stopped Finished: FAILURE
