Indeed a bug. The problem only exists with versions that are exactly
"SNAPSHOT" and only for the pom files.
I created an issue <https://issues.jfrog.org/jira/browse/HAP-106> and fixed
it for the next release.
Thanks
Yossi
On Sat, Nov 13, 2010 at 18:30, Yossi Shaul <[email protected]> wrote:
> Snapshot repository is selected when the file path contains "-SNAPSHOT". I
> think this
> is a mistake, and we should check the version string explicitly (if it's
> available) or the target
> path. If you can, please open a bug at
> https://issues.jfrog.org/jira/browse/HAP.
> I will try to reproduce this issue locally.
>
> Thanks,
> Yossi
>
>
> On Sat, Nov 13, 2010 at 01:10, deaddowney <[email protected]> wrote:
>
>>
>> I'm attempting to do a post-build deployment of artifacts using
>> Artifactory
>> and it looks like it's attempting to deploy to both my release and
>> snapshot
>> repositories:
>>
>> channel stopped
>> Deploying artifacts to http://build2.acme.com:8081/artifactory
>> Deploying artifacts of module: com.acme:Widgets
>> Deploying artifact:
>>
>> http://build2.acme.com:8081/artifactory/libs-snapshots-local/com/acme/Widgets/SNAPSHOT/Widgets-SNAPSHOT.jar
>> Deploying artifact:
>>
>> http://build2.acme.com:8081/artifactory/junk-releases-local/com/acme/Widgets/SNAPSHOT/Widgets-SNAPSHOT.pom
>> ERROR: Failed to deploy file: HTTP response code: 409. HTTP response
>> message: The repository 'junk-releases-local' rejected the artifact
>> 'junk-releases-local:com/acme/Widgets/SNAPSHOT/Widgets-SNAPSHOT.pom' due
>> to
>> its snapshot/release handling policy.
>> java.io.IOException: Failed to deploy file: HTTP response code: 409. HTTP
>> response message: The repository 'junk-releases-local' rejected the
>> artifact
>> 'junk-releases-local:com/acme/Widgets/SNAPSHOT/Widgets-SNAPSHOT.pom' due
>> to
>> its snapshot/release handling policy.
>>
>> junk-releases-local has a policy of only accepting releases and
>> libs-snapshots-local has a policy of only accepting SNAPSHOT releases. In
>> Hudson, target-releases-repo is set to junk-releases and
>> target-snapshots-repo is set to libs-snapshots-local.
>>
>> Has anyone run into this issue? It's not a consistent problem, only for
>> certain projects.
>> --
>> View this message in context:
>> http://forums.jfrog.org/Artifactory-Hudson-plugin-deploying-to-two-repositories-tp5734275p5734275.html
>> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Centralized Desktop Delivery: Dell and VMware Reference Architecture
>> Simplifying enterprise desktop deployment and management using
>> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
>> client virtualization framework. Read more!
>> http://p.sf.net/sfu/dell-eql-dev2dev
>> _______________________________________________
>> Artifactory-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>
>
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users