Re: oddity

2009-06-17 Thread Gilbert Rebhan
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

Re: oddity

2009-06-17 Thread Stefan Bodewig
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

RE: oddity

2009-06-17 Thread Rebhan, Gilbert
-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

RE: oddity

2009-06-17 Thread Rebhan, Gilbert
-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

Re: oddity

2009-06-17 Thread Stefan Bodewig
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,

RE: oddity

2009-06-16 Thread Rebhan, Gilbert
et or is blank = xmlkey set and != null xmlkey not set Any other ideas ? Should i open a bugreport ? Regards, Gilbert -Original Message- From: Rebhan, Gilbert Sent: Monday, June 15, 2009 4:15 PM To: 'Ant Users List' Subjec

oddity

2009-06-15 Thread Rebhan, Gilbert
Hi, found another oddity after upgrading to Ant 1.7.1, regarding the handling of properties and xmlproperties. ${ant.version} $${xmlkey} == ${xmlkey} $${txtkey} == ${txtkey} xmlkey set and != null xmlkey

Re: Another Oddity with Anthill OS

2007-01-18 Thread Res Pons
Great thanks, I will give it a try. Original Message Follows From: Steve Loughran <[EMAIL PROTECTED]> Reply-To: "Ant Users List" To: Ant Users List Subject: Re: Another Oddity with Anthill OS Date: Thu, 18 Jan 2007 10:07:12 + Res Pons wrote: Asking this question

Re: Another Oddity with Anthill OS

2007-01-18 Thread Steve Loughran
Res Pons wrote: Asking this question again. Is there anyway to force-load a diffrent property file in Anthill project property sheet even the build.xml loads one by default? In the build.xml file I already tell it to load .build.properties and on a DOS cmnd line I can supercede it by doing a

RE: Another Oddity with Anthill OS

2007-01-17 Thread Res Pons
PROTECTED]> Reply-To: "Ant Users List" To: [EMAIL PROTECTED] CC: user@ant.apache.org Subject: Another Oddity with Anthill OS Date: Sat, 13 Jan 2007 15:25:18 -0800 I'm testing a dummy project which checks out a basic simple project out of Subversion and echoes bunch of paths. T

Another Oddity with Anthill OS

2007-01-13 Thread Res Pons
I'm testing a dummy project which checks out a basic simple project out of Subversion and echoes bunch of paths. The purpose of this project is to see if I can force loading different property fiels at the command line via Anthill. Basically, I would like to use the same project 3x but each tim