Nevermind. I found out what the problem was.
In case anyone wonders, the problem occurred because I didn't deploy the
jar POM. This were not Maven artifacts so they had no POMs.
So, I created a minimal POM for them and redeployed each artifact with its
own minimal POM and now I'm retrieving the snapshots with no problem.
Cheers.
On Tue, Nov 1, 2011 at 3:19 PM, Nicky Ramone <[email protected]> wrote:
> Hi
>
> I have snapshot projects building continuously and deployed to artifactory
> with the "unique" snapshot policy (non-unique is not acceptable since we
> use Maven 3).
> The following dependency fails to be retrieved from Artifactory:
> <dependency>
> <groupId>com.dummy</groupId>
> <artifactId>foobar</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
>
> This seems to fail because in Artifactory it is deployed as
> foobar-1.0-20111031.193027-1.jar due to the "unique snapshot" policy.
> Of course, if i correct my POM and define it like:
> <dependency>
> <groupId>com.dummy</groupId>
> <artifactId>foobar</artifactId>
> <version>1.0-20111031.193027-1</version>
> </dependency>
>
> it works fine, but it loses the advantage that a snapshot provides because
> I won't get the updates.
> It looks like Artifactory is not handling correctly requests to *-SNAPSHOT.
>
> Would you know what could be occurring here and advise on how to proceed?
> Thanks very much.
>
> Regards.
>
------------------------------------------------------------------------------
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
