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 wrote:
On 2009-07-23, Nestor Dutko wrote:
This is the explicit extract of the declarations - as you
can see
On 2009-07-23, Nestor Dutko wrote:
> This is the explicit extract of the declarations - as you can see
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
These
3, 2009 12:40 AM
To: user@ant.apache.org
Subject: Re: Overriding previous definition of reference to ...
On 2009-07-22, Nestor Dutko 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
On 2009-07-22, Nestor Dutko 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 version
in non-executed targets.
Is this just not going away?
-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: Wednesday, July 22, 2009 10:06 AM
To: user@ant.apache.org
Subject: Re: Overriding previous definition of reference to ...
On 2009-07-22, Nestor Dutko wrote
On 2009-07-22, Nestor Dutko wrote:
> I understand that structures are not interpretted at runtime
> but are parsed
[in 1.6.x, this has changed in 1.7.x]
> and this is where the message is coming from. Is there a way to
> prevent this from occurring and yet retain the centralized
> definition o
rojects) is used to drive the overall
product build. I find that we see msgs of the form:
Overriding previous definition of reference to ocm.jsse.classpath when a
target nests (antcalls') out to another subtarget and the subtarget is in
one of these subprojects.
I understand that struct
