My guess is that your ivy:install target is wrong, it should be:

    <ivy:install
      organisation="apache"
      module="commons-lang"
      revision="2.3"
      from="maven"
      to="local"/>Don't forget to clean your cache before giving it a try!

regards,
Maarten



----- Original Message ----
From: Stephen Haberman <step...@exigencecorp.com>
To: ivy-u...@ant.apache.org
Sent: Wed, November 17, 2010 5:12:30 PM
Subject: ParseException during install with namespaces

Hi,

I'm trying to use ivy:install and have it translate from one namespace
to another. E.g. translate ibiblio's commons-lang/commons-lang to
apache/commons-lang while installing it into a local repo.

I think it should work, but I'm getting this error:

[ivy:install]         ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:install]         ::          UNRESOLVED DEPENDENCIES         ::
[ivy:install]         ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:install]         :: commons-lang#commons-lang;2.3:
java.text.ParseException: inconsistent module descriptor file found in
'http://repo1.maven.org/maven2/commons-lang/commons-lang/2.3/commons-lang-2.3.pom':

bad organisation: expected='commons-lang' found='apache'; 

A ParseException at this point seems like a really odd thing to have
happen, so I'm not sure if I'm doing something wrong or if it's a bug.

I made a github repo that minimally reproduces the problem. If you
checkout [1], and run "ant install", you'll see the error.

You can see the ivysettings.xml I'm using at [2]. Note that I use a
custom cache location so it won't mess up your ~/.ivy2/cache if you try
it out.

Oddly enough, if I remove "m2compatible=true" from my ibiblio resolver
definition, the error goes away, and the install technically works, but
only the jar is installed, the sources are not picked up.

Shouldn't my use case still work with m2compatible=true?

Thanks,
Stephen

[1]: https://github.com/stephenh/ivy-install-test
[2]: https://github.com/stephenh/ivy-install-test/blob/master/ivysettings.xml


      

Reply via email to