You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Vasco Lemoine <va...@imc.nl> on 2008/02/22 13:25:36 UTC
modules get evicted when resolve is called the second time
Hi,
I'm experiencing strange behavior when resolving dependencies. The first
time I the resolve task is executed, after a <ivy:cleancache /> has been
performed, everything is fine. When I execute the resolve task again
modules are being evicted and the following error message( a lot) :
[ivy:resolve] ivy internal error: no node found for etc.
I hope based on the described symptoms you can give me some leads what
to look for.
Regards Vasco
Re: modules get evicted when resolve is called the second time
Posted by Vasco Lemoine <va...@imc.nl>.
Created Jira issue:
IVY-745
On Sat, 2008-02-23 at 11:32 +0100, Xavier Hanin wrote:
> Indeed, Ivy didn't help to find this out, could you please open an issue in
> JIRA to ask for the behavior in such case to be more consistent and easy to
> diagnose.
>
> Xavier
>
> On Fri, Feb 22, 2008 at 3:09 PM, Vasco Lemoine <va...@imc.nl> wrote:
>
> > Well I found out what is causing the problem but I think it is of
> > interest to share it.
> >
> > I introduced a extra attribute which I am using for building of
> > submodules.
> >
> > foo-ivy.xml:
> >
> > <ivy-module version='2.0'>
> > <info organisation='foo' module='foo' revision='1' />
> > <configurations>
> > <include file='${build_home}/etc/ivy/ivy-configurations.xml' />
> > </configurations>
> > <publications />
> > <dependencies>
> > <dependency org='bar' name='bar' rev='trunk' submodule='bar' />
> > </dependencies>
> > </ivy-module>
> >
> > bar-ivy.xml:
> >
> > <ivy-module version='2.0'>
> > <info organisation='bar' module='bar' revision='1' />
> > <configurations>
> > <include file='${build_home}/etc/ivy/ivy-configurations.xml' />
> > </configurations>
> > <publications />
> > <dependencies>
> > <dependency org='foobar' name='foobar' rev='1' />
> > </dependencies>
> > </ivy-module>
> >
> > Because the submodule attribute was missing in the bar-ivy.xml <info>
> > tag. The foobar dependency gets evicted. I'm not sure this is expected
> > behavior. If not it is probably a bug or at least the provided
> > information is not clear enough to troubleshoot. Of course the work
> > around is adding the extra attribute to the info tag:
> >
> > <ivy-module version='2.0'>
> > <info organisation='bar' module='bar' revision='1' submodule='bar' />
> > <configurations>
> > <include file='${build_home}/etc/ivy/ivy-configurations.xml' />
> > </configurations>
> > <publications />
> > <dependencies>
> > <dependency org='foobar' name='foobar' rev='1' />
> > </dependencies>
> > </ivy-module>
> >
> > Regards Vasco.
> >
> >
> > On Fri, 2008-02-22 at 13:25 +0100, Vasco Lemoine wrote:
> > > Hi,
> > >
> > > I'm experiencing strange behavior when resolving dependencies. The first
> > > time I the resolve task is executed, after a <ivy:cleancache /> has been
> > > performed, everything is fine. When I execute the resolve task again
> > > modules are being evicted and the following error message( a lot) :
> > >
> > > [ivy:resolve] ivy internal error: no node found for etc.
> > >
> > > I hope based on the described symptoms you can give me some leads what
> > > to look for.
> > >
> > > Regards Vasco
> > >
> > >
> > >
> >
> >
>
>
Re: modules get evicted when resolve is called the second time
Posted by Xavier Hanin <xa...@gmail.com>.
Indeed, Ivy didn't help to find this out, could you please open an issue in
JIRA to ask for the behavior in such case to be more consistent and easy to
diagnose.
Xavier
On Fri, Feb 22, 2008 at 3:09 PM, Vasco Lemoine <va...@imc.nl> wrote:
> Well I found out what is causing the problem but I think it is of
> interest to share it.
>
> I introduced a extra attribute which I am using for building of
> submodules.
>
> foo-ivy.xml:
>
> <ivy-module version='2.0'>
> <info organisation='foo' module='foo' revision='1' />
> <configurations>
> <include file='${build_home}/etc/ivy/ivy-configurations.xml' />
> </configurations>
> <publications />
> <dependencies>
> <dependency org='bar' name='bar' rev='trunk' submodule='bar' />
> </dependencies>
> </ivy-module>
>
> bar-ivy.xml:
>
> <ivy-module version='2.0'>
> <info organisation='bar' module='bar' revision='1' />
> <configurations>
> <include file='${build_home}/etc/ivy/ivy-configurations.xml' />
> </configurations>
> <publications />
> <dependencies>
> <dependency org='foobar' name='foobar' rev='1' />
> </dependencies>
> </ivy-module>
>
> Because the submodule attribute was missing in the bar-ivy.xml <info>
> tag. The foobar dependency gets evicted. I'm not sure this is expected
> behavior. If not it is probably a bug or at least the provided
> information is not clear enough to troubleshoot. Of course the work
> around is adding the extra attribute to the info tag:
>
> <ivy-module version='2.0'>
> <info organisation='bar' module='bar' revision='1' submodule='bar' />
> <configurations>
> <include file='${build_home}/etc/ivy/ivy-configurations.xml' />
> </configurations>
> <publications />
> <dependencies>
> <dependency org='foobar' name='foobar' rev='1' />
> </dependencies>
> </ivy-module>
>
> Regards Vasco.
>
>
> On Fri, 2008-02-22 at 13:25 +0100, Vasco Lemoine wrote:
> > Hi,
> >
> > I'm experiencing strange behavior when resolving dependencies. The first
> > time I the resolve task is executed, after a <ivy:cleancache /> has been
> > performed, everything is fine. When I execute the resolve task again
> > modules are being evicted and the following error message( a lot) :
> >
> > [ivy:resolve] ivy internal error: no node found for etc.
> >
> > I hope based on the described symptoms you can give me some leads what
> > to look for.
> >
> > Regards Vasco
> >
> >
> >
>
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
Re: modules get evicted when resolve is called the second time
Posted by Vasco Lemoine <va...@imc.nl>.
Well I found out what is causing the problem but I think it is of
interest to share it.
I introduced a extra attribute which I am using for building of
submodules.
foo-ivy.xml:
<ivy-module version='2.0'>
<info organisation='foo' module='foo' revision='1' />
<configurations>
<include file='${build_home}/etc/ivy/ivy-configurations.xml' />
</configurations>
<publications />
<dependencies>
<dependency org='bar' name='bar' rev='trunk' submodule='bar' />
</dependencies>
</ivy-module>
bar-ivy.xml:
<ivy-module version='2.0'>
<info organisation='bar' module='bar' revision='1' />
<configurations>
<include file='${build_home}/etc/ivy/ivy-configurations.xml' />
</configurations>
<publications />
<dependencies>
<dependency org='foobar' name='foobar' rev='1' />
</dependencies>
</ivy-module>
Because the submodule attribute was missing in the bar-ivy.xml <info>
tag. The foobar dependency gets evicted. I'm not sure this is expected
behavior. If not it is probably a bug or at least the provided
information is not clear enough to troubleshoot. Of course the work
around is adding the extra attribute to the info tag:
<ivy-module version='2.0'>
<info organisation='bar' module='bar' revision='1' submodule='bar' />
<configurations>
<include file='${build_home}/etc/ivy/ivy-configurations.xml' />
</configurations>
<publications />
<dependencies>
<dependency org='foobar' name='foobar' rev='1' />
</dependencies>
</ivy-module>
Regards Vasco.
On Fri, 2008-02-22 at 13:25 +0100, Vasco Lemoine wrote:
> Hi,
>
> I'm experiencing strange behavior when resolving dependencies. The first
> time I the resolve task is executed, after a <ivy:cleancache /> has been
> performed, everything is fine. When I execute the resolve task again
> modules are being evicted and the following error message( a lot) :
>
> [ivy:resolve] ivy internal error: no node found for etc.
>
> I hope based on the described symptoms you can give me some leads what
> to look for.
>
> Regards Vasco
>
>
>