I already thinked to something like that. And to be complete, the test should also do a resolve using maven libraries and compare that resulting jars.
However, that would make really a lot of download :-) Gilles > -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Sent: mercredi 10 octobre 2007 14:08 > To: [email protected] > Subject: testing ivy by walking the repository > > > > Ivy 2.0.0-alpha-2 isnt working with slf4j: > > <dependency org="org.slf4j" > name="slf4j-jcl" > rev="1.4.3" > conf="redist->default"/> > > [ivy:resolve] :::: WARNINGS > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] :: UNRESOLVED DEPENDENCIES :: > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] :: [ org.slf4j | slf4j-jcl | 1.4.3 ]: > java.text.ParseException: inconsistent module descriptor file found in > 'http://repo1.maven.org/maven2/org/slf4j/slf4j-jcl/1.4.3/slf4j-jcl-1.4.3.pom': > bad revision: expected='1.4.3' found='${parent.version}'; > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] :::: ERRORS > [ivy:resolve] maven2: bad revision found in > http://repo1.maven.org/maven2/org/slf4j/slf4j-jcl/1.4.3/slf4j-jcl-1.4.3.pom: > expected='1.4.3 found='${parent.version}' > [ivy:resolve] > > > This has made me think of an interesting little field test: enumerating > the entire ibiblio m2 repository, and having ivy try and parse every > single pom file there. Has anyone tried this? We'd need something to > autogenerate the ivy.xml files, then throw then one by one at ivy, > presumably creating a junit test suite on the fly to do this... > > -- > Steve Loughran http://www.1060.org/blogxter/publish/5 > Author: Ant in Action http://antbook.org/
