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="resolved.build.dependencies.path">
<fileset dir="${build.jar.dir}">
<include name="**/*.jar"/>
</fileset>
</path>
But when I used later in the ant script like this "<path refid="
resolved.build.dependencies.path"/>" 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 <[EMAIL PROTECTED]> 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="resolved.build.dependencies.path"/>
And I can do a basic manipulation (immediately afterward in the file)
such as :
<pathconvert property="resolved.build.dependencies"
refid="resolved.build.dependencies.path"></pathconvert>
However, if I do this later in the file I get the following message:
"Reference resolved.build.dependencies.path not found."
Any thoughts on why the path would appear to go out of scope ?
Thanks
Jim Mochel
--
Regards,
John Gill
