Hi Oliver,
Changing from unique to non-unique should only affect future deployments of
snapshots.
This is because maven is using the maven-metadata.xml to determine which
snapshot
to download (either a unique or non-unique). And this file is generated by
Artifactory upon
deployment. So if you used non-unique snapshots and than switched to unique,
the maven
metadata of already deployed snapshots will still point to the unique
snapshot version.
How does the maven-metadata.xml looks like for version that does not work?
(you can check it in the repo browser, select the folder that contain the
snapshot versions
and then the metadata tab). Does it contain unique, non-unique or both?
Yossi
On Wed, Aug 25, 2010 at 5:08 PM, o.stauss <[email protected]> wrote:
>
> Hello,
> in our old artifactory we used repository with (painfull) unique snapshot
> policy.
>
> We want to change the the policy to "non-unique" !!!
>
> One of the effect is that maven is no longer able to resolve such an
> dependency:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) xxx:yyy:zzz
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=xxx -DartifactId=yyy -Dversion=zzz
> -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=xxx -DartifactId=yyy -Dversion=zzz
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) aaa:bbb:ccc
> 2) xxx:yyy:zzz
>
> ----------
>
> Questions:
> is it possible to "covert" the formerly unique-snapshot-artifacts in
> non-unique-snapshot-artifacts?
>
> Idea:
> a) I tried to export an unique-snapshot repository and then import into an
> non-unique-snapshot repository --> no effect artifacts comes from import
> with the evil timestamp .....
>
> a1) same as a) but before import use a local script, that rename (using
> regex) the unique timestamps from the export on the file-system, delete
> wrong meta-infos and do then the import --> very tricky and risky?
>
> b) don't switch the repository from "unique-snapshot" to
> "non-unique-snapshot", bit set the maxUniqueSnapshots property to "1" -->
> even as evil as do nothing IMHO
>
> c) a background process will do the work for me :-)
>
> ==> any tips / ideas / solutions
>
> regards Oliver
> --
> View this message in context:
> http://forums.jfrog.org/convert-formerly-unique-snapshot-repository-to-a-non-unique-snapshot-repository-tp5461423p5461423.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
