maven deploy:deploy-file fails (409 Conflict), yet artifact uploads successfully

Question

NOTE:

I now realize that the jar got placed into my repository, but the pom.xml did not. Now, I have another project where the pom.xml fails to

Answer 1

In my case the POM file associated with the jar file (external, in same dir) had a dependency to itself. This was a offline zipped repo from a third party that I needed to load into artifactory.

I modified the POM files, removed the self-dependency and made sure the package info was right. Then artifacts deployed with no problems. Sent email to vendor so they can fix in their build.

Answer 2

There is a good possibility that the space on your remote repo is full. Verify that before going all technical and wasting time. Wasted 2-3 hrs thinking its a logical problem.

Answer 3

I also face this problem, and I found the reason is the parent project didn't deploy in the snapshot repository. I run mvn deploy in the parent folder, and the problem resolved.

Answer 4

Yeah....Multiple Reason for same error. May be it will help somebody

1. Login as Admin to Artifactory
2. Configuration -> Repositories
3. Edit the Local Repository ---> Suppress POM Consistency Checks

This solves my problem.... Not sure. Right approach or not ?

Answer 5

Ensure that you include -SNAPSHOT as part of your version if you are publishing to snapshot repository.

Answer 6

Had that error message too. For me the problem was that the setup of the server is to accept only release, not SNAPSHOT. After removing the SNAPSHOT from the pom, it worked fine.