Re: [Artifactory-users] maven deploy:deploy-file fails (409 Conflict), yet artifact uploads successfully

[David W. <qa...@gm...>]

Yes, thanks. I changed the repo I was sending things to from ext-release-repo to lib-release-repo, and the configuration on lib-release-repo had the Pom Consistency check on. That meant that if the pom.xml had one version, but I put another version on the command line, the pom.xml was rejected (but not the jar file).

The error message that just said "Conflict" was throwing me off. Interesting, if I replaced an existing version, the new jar was put in, but the old pom.xml wasn't replaced or removed.

The other problem was the developer marked the jar as a SNAPSHOT, and I hadn't considered this as a possibility. We mainly use Ivy which doesn't have the SNAPSHOT concept. I generate the pom.xml from the ivy.xml file and use "mvn deploy:deploy-file" to put it in the repository as a Maven jar.

So, that was another issue once I figured the pom consistency check needed to be turned off. I then got "forbidden" as a error message. Took me a while to realize why.

I wish the error messages were a bit more clear. For example: "pom.xml and -Dversion don't match" vs. "Conflict" or "Can't store snapshot in release repo" instead of merely saying "forbidden".

On Oct 7, 2012, at 5:02 AM, Noam Y. Tenne <no...@jf...> wrote:

> I see in the SO post that you've found the cause of these errors; has this issue been resolved?
> 
> On Fri, Oct 5, 2012 at 4:58 PM, David Weintraub <qa...@gm...> wrote:
> I've already posted this on StackOverflow:
> http://stackoverflow.com/q/12734788/368630. It was recommended to post
> it here too.
> 
> I have a jar file and a pom.xml file I want to deploy to Artifactory.
> I do the following command:
> 
>     mvn deploy:deploy-file -Dversion=0.8.0 \
>         -Dfile=project.jar -DpomFile=pom.xml
>         -Durl=http://buildl01.tcprod.local/artifactory/ext-release-local \
>         -DrepositoryId=VegiBank
> 
> And I get the which I've placed in pastebin: http://pastebin.com/4KEkswbA
> 
> The jar file gets put into Artifactory in the correct place, but the
> pom.xml does not come over. Instead, I get the error:
> 
> I've finally traced the error to the fact that the `-Dversion="0.8.0"
> doesn't equal the <version>0.8.0-CI</version> tag. Previously, I was
> able to override the <version> tag in the pom.xml with the command
> line. However, it now appears that this is no longer the case.
> 
> Is there a setting in Artifactory where I can override the <version>
> tag in the pom.xml?
> 
> 
> --
> David Weintraub
> qa...@gm...
> 
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Artifactory-users mailing list
> Art...@li...
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
> 
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev_______________________________________________
> Artifactory-users mailing list
> Art...@li...
> https://lists.sourceforge.net/lists/listinfo/artifactory-users