I see the same problems with wildcards using the command-line technique:
With an ivysettings.xml like:
<ivysettings>
<settings defaultResolver="url"/><!-- "ext" -->
<resolvers>
<url name="url" m2compatible="true">
<artifact
pattern="http://artifacts.netflix.com/ext-release-local/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]";
/>
</url>
<filesystem name="ext" m2compatible="false" descriptor="optional"
checkconsistency="false">
<artifact pattern="${ext.libs}/[artifact]-[revision].[ext]" />
</filesystem>
</resolvers>
</ivysettings>
And ${ext.libs} point to a dir full of jars and -ivy.xml files like:
commons-collections-3.2.1.jar.
Command:
java -jar ivy-2.1.0-rc2.jar -settings ivysettings.xml -dependency
commons-collections commons-collections '[3.2,4.0)'
Yields:
module not found:
commons-collections#commons-collections;[3.2,4.0)
But using the "ext" resolver yields:
found commons-collections#commons-collections;3.2.1 in ext
[3.2.1] commons-collections#commons-collections;[3.2,4.0)
--
View this message in context:
http://www.nabble.com/Ivy-resolving-wildcard-revisions-w--Artifactory-tp25394756p25462143.html
Sent from the Artifactory-Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
