Hi! Thanks for your answer.
Alright, I'll try that. Actually this is not an issue anymore because we
will disable releases on snapshots repositories. I just wanted to know if
that was a common error.
Btw, how bad is to disable pom consistency check on the repository?
Vitor
On Sun, May 6, 2012 at 9:16 AM, Yossi Shaul <[email protected]> wrote:
> Hi Victor,
>
> The 409 might be a result of another problem with the pom file which is
> not related to the snapshot/release policy.
> Maven doesn't display the HTTP status message which migh explain what went
> wrong. Try downloading from the browser or with curl and you'll be able to
> see the status message.
> My guess is that the pom is invalid and hence rejected by Artifactory. If
> this is the case you can either manually deploy a fixed version of the pom
> or disable the pom consistency
> check<http://wiki.jfrog.org/confluence/display/RTF/Local+and+Remote+Repositories>for
> this repository.
>
>
> HTH
>
> Yossi
>
> On Fri, May 4, 2012 at 8:25 PM, Vitor Miranda <[email protected]>wrote:
>
>> Hello guys. I've posted this issue on Maven users, but I was recommended
>> to do the same here.
>>
>> Short story:
>>
>> If I have releases enabled = true on my snapshot repo configuration (my
>> settings.xml), and the snapshot repository is properly configured (aka,
>> only handle Snapshots, not Releases), I get the 409 when adding
>> dependencies which are releases (read below for details). If releases
>> enabled = false, no problems. After a while I tried marking my Snapshot
>> repo to handle Releases aswell, with releases enabled=true on client side:
>> works fine!
>>
>> ----------------
>>
>> "The error:
>>
>> "ArtifactDescriptorException: Failed to read artifact descriptor for
>> javax.faces:jsf-api:jar:1_1_01: ArtifactResolutionException: Could not
>> transfer artifact javax.faces:jsf-api:pom:1_1_01 from/to snapshots-repo (
>> http://ip/artifactory/snapshots-repo): Failed to transfer
>> http://ip/artifactory/snapshots-repo/javax/faces/jsf-api/1_1_01/jsf-api-1_1_01.pom.
>> Error code 409, Conflict"
>>
>> Hi!
>>
>> Anyone know exactly what happens when you set
>> <snapshots|releases><enabled>true</enabled></snapshots|releases> on the
>> repository section? The documentation and my intuition said that, if you
>> set one to false, Maven won't even care to search/download the specified
>> type of artifact from that repository. If it's true, Maven will look on
>> that repository for that type of the artifact . If it doesn't find, just go
>> on and look on other repositories, if any are defined. Fair enough to me,
>> but I had this issue which took me hours to solve:
>>
>> We have four repositories.
>>
>> - Snapshots
>> - Releases (which is empty so far)
>> - External
>> - Release/Legacy (was the first repo created, will migrate to External
>> soon)
>>
>> The first two are what they are meant to, External is a repository for
>> the 3rd party artifacts that we use (no snapshots there) and Legacy also
>> has 3rd party artifacts (no snapshots also). Then there's this POM which
>> references three other POMs, which then have dependencies. All were
>> deployed on the Snapshots repo. Some of the jar dependencies were on
>> legacy, others on external. I was getting the infamous 409 - Conflict at 3
>> or 4 artifacts when adding one of the "super poms" as a dependency -
>> doesn't happen when adding a specifc jar dependency.
>>
>> Solution: set <releases><enabled>false</enabled></releases> on the
>> snapshots repo configuration.
>>
>> Why? I don't get this. It's ok to filter releases/snapshots to the
>> correct repositories, but why this error? To show an example: when adding
>> the highest parent pom, I get the 409 I pasted above on 4 artifacts. All of
>> those are on legacy, and none is a snapshot. So maven tries to get a
>> release-type artifact from a snapshot repo only. Obviously there's nothing
>> there (but I didn't specify Maven to not get from it (enabled is true), so
>> it's ok). What I'd expect to happen: can't find the artifact here (which,
>> in case, there actually ISN'T any similar artifact there), I'll just move
>> to the other repositories. What happens: 409.
>>
>> At least we found a solution, but I'd appreciate any help on
>> understanding this issue.
>>
>> Thanks!"
>>
>> ----------------------
>>
>> After sending that to Maven users I found out that by checking the
>> snapshot repo to handle releases on artifactory, with or without releases
>> enabled on my snapshot repo settings, the 409 is gone.
>>
>> Is this an expected behavior?
>>
>> Thanks!
>>
>> --
>> Vitor Branco de Miranda
>> BCC - UFSCar - São Carlos/SP
>> +55 19 92013531
>> [email protected]
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Artifactory-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
--
Vitor Branco de Miranda
BCC - UFSCar - São Carlos/SP
+55 19 92013531
[email protected]
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
