Artifactory 2.2.1 + Hudson + Maven

Artifactory 2.2.1 and Hudson - error

I have just recently updated my Artifactory from version 2.0.7 to version 2.2.1 and immediately my release builds done from Hudson using the Hudson Release Plugin started failing with a nasty error message (line breaks added manually for readability).

ERROR: Error deploying artifact:
Resource to deploy not found: File:
console-0.1.24-SNAPSHOT.pom does not exist

org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Resource to deploy not found: File: http://*/artifactory/libs-releases-local/*/0.1.24-SNAPSHOT/console-0.1.24-SNAPSHOT.pom does not exist
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:119)
at hudson.maven.reporters.MavenAggregatedArtifactRecord.deploy(MavenAggregatedArtifactRecord.java:79)
at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:96)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:582)
at hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:563)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:594)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
at hudson.model.Run.run(Run.java:1221)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:122)
Caused by: org.apache.maven.wagon.TransferFailedException: Resource to deploy not found: File: http://*/artifactory/libs-releases-local/*/0.1.24-SNAPSHOT/console-0.1.24-SNAPSHOT.pom does not exist
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:283)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
... 12 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: File: http://*/artifactory/libs-releases-local/*/0.1.24-SNAPSHOT/console-0.1.24-SNAPSHOT.pom does not exist
at org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:168)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
... 14 more

It normally helps to see the Artifactory system log. Here is what I found in mine:

2010-02-18 13:48:10,732 [http-8000-3] [WARN ] (o.a.r.j.StoringRepoMixin:543) -
IO error while trying to save resource libs-releases-local:
The target deployment path '*/0.1.15-SNAPSHOT/console-0.1.15-SNAPSHOT.pom'
does not match the POM's expected path prefix '*/0.1.16-SNAPSHOT'.
Please verify your POM content for correctness and make sure the source path is a valid Maven 2 repository root path.

But that's easy to fix with the following command:


You should pass it to your server that runs Artifactory.

However, I also found this:

2010-02-18 13:48:10,732 [http-8000-3] [ERROR] (o.a.j.l.SessionLockEntry:266) -
Immutable item /repositories/libs-releases-local*/0.1.15-SNAPSHOT/console-0.1.15-SNAPSHOT.pom has local modifications that will be ignored.

I found this call in the Artifactory source code but that didn't really give me any clues...

Anyway, the release builds were still failing and luckily I managed to find a workaround.

The workaround

The workaround is a simple operation to be done in Hudson actually (not in Artifactory). In your project configuration there might be two check boxes:
  • Deploy artifacts to Maven repository
  • Deploy artifacts to Artifactory

The workaround for this issue is: uncheck both check boxes. Easy does it.


  1. Hi Michal,

    The first error you got from Artifactory is a safeguard against deploying a pom to the wrong coordinates (in your case, snapshot 0.1.16 to the coordinates of snapshot 0.1.15). If you wish to remove it, this can be done via the UI (no need to use -D). Simply - in the repo config panel, open the 'Advanced' sub panel and select 'Suppress POM Consistency Checks'.
    Since you have the 'Deploy to Artifactory' option available in Hudson, you have the Artifactory Hudson plug-in installed - using if for deployment will give you a 2-way fully traceable build and a more reliable multi-module deployment (see: http://wiki.jfrog.org/confluence/display/RTF/Build+Integration). If you don't wish to loose this functionality, you may be able to run the release plugin in a separate job - maybe as a downstream job of the one deploying. Just a sugggestion :)



  2. Yoav, thank you for your message! I will check out the Suppress POM Consistency Checks option tomorrow.

    Yes, I do have the Artifactory Hudson plugin installed. Can I use it to release (Maven kind of release) with version number bumping though?