ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Gill" <>
Subject Re: Starngely non-referenceable path from cachepath
Date Thu, 22 Feb 2007 13:22:01 GMT
This might be a long shot, but I seem to remember having a similar problem
with path refid's in ANT (although I was using IVY as well) and spent quite
some time trying to figure it all out. I came to the conclusion that the
pathid name was too long or something, so I shortened it to "lib-path" or
something like that, and then it started working for me.

Basically, I had something like:
<path id="">
    <fileset dir="${build.jar.dir}">
       <include name="**/*.jar"/>

But when I used later in the ant script like this "<path refid=""/>" I got a similar message that you got.

After stuffing around for a while, I simply changed the name of the id to
"lib-path" and it started working. So try shortening the name if the refid.

On 2/22/07, James Mochel <> wrote:
> I have been happily using IVY on a large project and I just ran into a
> gotcha.
> In my build file I use this to create a path with all the resolved
> <ivy:configure file="${commonbuild.root.dir}/ivyconf.xml"
> validate="true" />
> <ivy:resolve validate="true"/>
> <ivy:cachepath pathid=""/>
> And I can do a basic manipulation (immediately afterward in the file)
> such as :
> <pathconvert property=""
> refid=""></pathconvert>
> However, if I do this later in the file I get the following message:
> "Reference not found."
> Any thoughts on why the path would appear to go out of scope ?
> Thanks
> Jim Mochel

John Gill

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message