Thanks Stefan, I will try and come up with a small reproducible test
case.
-- Nestor
On Jul 24, 2009, at 10:11 AM, Stefan Bodewig <bode...@apache.org> wrote:
On 2009-07-23, Nestor Dutko <nestor.du...@oracle.com> wrote:
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>
These definitions are not causing the warning, the (or rather a) place
where you use refid="ocm.jsse.classpath" is.
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?
It shouldn't be, no. You may have hit a bug although I'm unbale to
reproduce it myself.
On 2009-07-22, Nestor Dutko <nestor.du...@gmail.com> wrote:
Trying to determine the cost of picking up ant 1.7.0, I tried this
and found
now that I get the warning -
I'll note that Ant 1.7.1 is the current version and I don't have Ant
1.7.0 installed right now.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-h...@ant.apache.org
