Ivy and Maven have different syntax for version ranges. Also the semantics are different. Gradle currently doesn't abstract over this. This can become a problem when both Ivy and Maven repositories are used in the same build.
I've just tried to resolve "junit:junit-dep:[4.7,4.99]" from Maven Central, and it worked fine. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/Can-not-resolve-artifacts-with-dynamic-revisions-from-Ivy-repository-tp5680421p5683614.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
