Yes I confirm that Maven Central works as expected and has no problems with dynamic revisions. Had hope that the problem with Ivy is that I use Maven Central in buildscript closure to resolve io:commons-io but this was not the case. I turned the Maven repository off and still it ends up with Could not find any version that matches group:commons-beanutils, module:commons-beanutils, version:1.8.+. Giving a explicit version number like 1.8.3 resolves correct .
I also agree that this should not be a k.o criterion not changing from ant/gant/ivy to gradle but still I would like to know if this should be possible or not. For the moment I resolve the dependencies with a gant script and set up gradle to use the users ivy cache as the 'repository'. ~ Milan -- View this message in context: http://gradle.1045684.n5.nabble.com/Can-not-resolve-artifacts-with-dynamic-revisions-from-Ivy-repository-tp5680421p5684851.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
