That't not quite what I am seeing though.
This is the explicit extract of the <path> declarations - as you can see
<path id="ocm.jsse.classpath">
<fileset dir="${ocm.dependencies.root}/ocm_common">
<include name="jsse.jar"/>
</fileset>
</path>
<path id="ocm.jsse-support.classpath">
<fileset dir="${ocm.dependencies.root}/ocm_common">
<include name="jcert.jar"/>
<include name="jnet.jar"/>
</fileset>
</path>
<path id="ocm.jce-support.classpath">
<fileset dir="${ocm.dependencies.root}/ocm_collector">
<include name="osdt_core3.jar"/>
<include name="osdt_jce.jar"/>
</fileset>
</path>
And all of the files include the common.xml as the first element within it
using the ENTITY reference ('&common;')
Its important to note that the <path> definitions reside OUTSIDE of a target.
Is this the problem?
-----Original Message-----
From: Stefan Bodewig [mailto:[email protected]]
Sent: Thursday, July 23, 2009 12:40 AM
To: [email protected]
Subject: Re: Overriding previous definition of reference to ...
On 2009-07-22, Nestor Dutko <[email protected]> wrote:
> Trying to determine the cost of picking up ant 1.7.0, I tried this and found
> now that I get the warning -
> Warning: Reference ocm.jsse.classpath has not been set at runtime, but was
> found during
> build file parsing, attempting to resolve. Future versions of Ant may
> support
> referencing ids defined in non-executed targets.
> Is this just not going away?
8-)
The warning means you are using a path via refid somewhere in the
build file before said path has been defined - at least if Ant doesn't
define ids during parser time.
You should fix that, because Ant 1.8.0 (no release plan, yet) will no
longer find the path.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
