Which version of ivy are you using ? Work as been donne on 2.3 to fix those
kind of problem. As far as i know 2.3 is not yet released but toi can try a
nightly or rc.
Le 12 juin 2012 07:08, "Mitch Gitman" <mgit...@gmail.com> a écrit :
> I adapted src/example/multi-project in the Ivy distribution to have the
> existing Ivy modules extend a parent ivy.xml. Such as:
> <ivy-module version="1.0">
> <info
> organisation="org.apache.ivy.example"
> module="find"
> status="integration">
> <extends organisation="org.apache.ivy.example"
> module="multi-parent" revision="1.0"
> location="../multi-parent/ivy.xml" />
> </info>
>
> Both absolute and relative paths worked.
>
> This suggests the problem is on my end. I'm going to try deconstructing the
> failing modules next, but if this rings any bells, I'd be glad to hear.
>
> On Mon, Jun 11, 2012 at 11:13 AM, Mitch Gitman <mgit...@gmail.com> wrote:
>
> > I'm using the parent Ivy module feature with the ivy.xml
> > /ivy-module/info/extends element. This works just fine whether I use a
> > relative path or an absolute path for the location attribute that locates
> > the parent ivy.xml. When I go to run ivy:buildlist, however, it only
> works
> > with the relative path. The moment it encounters an absolute path for the
> > parent location, it fails with:
> > … impossible to parse ivy file for …: ivyfile=…/ivy.xml
> > exception=java.text.ParseException: Problem occurred while parsing ivy
> > file: Unable to
> > parse included ivy file for …#...;… in file:/…/ivy.xml
> >
> > The exception is being thrown in XmlModuleDescriptorParser, line 422:
> > if (parent == null) {
> > throw new ParseException("Unable to parse included ivy
> > file for "
> > + parentOrganisation + "#" + parentModule + ";" +
> > parentRevision, 0);
> > }
> >
> > I'm seeing this with Ivy 2.2.0. I haven't tried yet to reproduce it with
> > Ivy 2.3.0-rc1.
> >
> > Is anyone familiar with this behavior? Is this a known bug or is there
> > something I'm missing?
> >
> > Depending on what I hear back, I can try creating an isolated, simple use
> > case using both 2.2.0 and 2.3.0-rc1.
> >
>
