You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-dev@incubator.apache.org by Steve Loughran <st...@apache.org> on 2007/10/10 12:07:59 UTC
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/
Re: testing ivy by walking the repository
Posted by Xavier Hanin <xa...@gmail.com>.
On 10/10/07, Steve Loughran <st...@apache.org> wrote:
>
>
>
> 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]
BTW, could you open an issue for that?
Xavier
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/
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: testing ivy by walking the repository
Posted by Xavier Hanin <xa...@gmail.com>.
On 10/10/07, Gilles Scokart <gs...@gmail.com> wrote:
>
>
> 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.
It would be an interesting test, at least it would allow to say exactly how
much we are compatible with maven 2 (50%, 80%, ...). ATM we now that there
are several remaining problems, I think the most important ones are error in
parsing (as slf4j's case). Then we have many other issues but which may not
be that much important in frequency of use:
- dependency management section (recently reported by a user)
- parent pom handling
- profiles (which would require conditional configurations or dependencies).
Xavier
However, that would make really a lot of download :-)
>
> Gilles
>
>
> > -----Original Message-----
> > From: Steve Loughran [mailto:stevel@apache.org]
> > Sent: mercredi 10 octobre 2007 14:08
> > To: ivy-dev@incubator.apache.org
> > 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/
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
Re: testing ivy by walking the repository
Posted by Steve Loughran <st...@apache.org>.
Gilles Scokart wrote:
> 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.
well, I think they use different algorithms. However, it makes a good
regression test too.
> However, that would make really a lot of download :-)
yes and no.
1. You only need to pull the poms down, not the artifacts
2. if you have a local cache (we do, but it doesn't update very often)
3. the maven results could be stored somewhere in one big file
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
RE: testing ivy by walking the repository
Posted by Gilles Scokart <gs...@gmail.com>.
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:stevel@apache.org]
> Sent: mercredi 10 octobre 2007 14:08
> To: ivy-dev@incubator.apache.org
> 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/