Stefan Bodewig schrieb:
> On 2009-06-17, Rebhan, Gilbert wrote:
>
>> It wasn't an issue with jdk, but the processNode Method in XmlProperty
>
>> if (nodeText.trim().length() != 0 || emptyNode) {
>> addProperty(prefix, nodeText, id);
>> }
>
>> when trim removes all whi
On 2009-06-17, Rebhan, Gilbert wrote:
> It wasn't an issue with jdk, but the processNode Method in XmlProperty
> if (nodeText.trim().length() != 0 || emptyNode) {
> addProperty(prefix, nodeText, id);
> }
> when trim removes all white spaces, so it works with
> if (n
-Original Message-
From: Rebhan, Gilbert
Sent: Wednesday, June 17, 2009 1:58 PM
To: 'Ant Users List'
Subject: RE: oddity
/*
Bugreport opened, Patch attached =
https://issues.apache.org/bugzilla/show_bug.cgi?id=47381
[...]
Works with ant 1.7.1, jdk 1.5.0_11 and jdk 1
-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: Wednesday, June 17, 2009 9:49 AM
To: user@ant.apache.org
Subject: Re: oddity
/*
On 2009-06-16, Rebhan, Gilbert wrote:
> Conclusion = there seems to be a difference related to the handling
> of tx
On 2009-06-16, Rebhan, Gilbert wrote:
> Conclusion = there seems to be a difference related to the handling
> of txt- and xmlproperties on different platforms, maybe it's caused
> by jdk/jre ?
Looked like a Java5/Java6 difference, maybe inside the XML parser.
> Should i open a bugreport ?
Yes,
followup =
the behaviour described in my first posting occurs with Windows2000, jdk
1.5.0_11
i checked with the same propertyfiles, means
txtkey= *blank*
and antscript with isset condition on my private machine =
OpenSuse 11.1/64bit, jdk 1.6.0_13 and got equal ouput for all available ant
