Re: Problems resolving paths in copy's "tofile" when combining multiple properties

2010-03-03 Thread Oliver Schrenk
Ouch. You are right of course. Good thing is that I learned about the difference about "value" and "location", even If I had to learn it the hard way through public humiliation. Thanks for taking the time. Am 03.03.2010 um 17:01 schrieb Antoine Levy Lambert: > Hello Oliver, > > on mac, becaus

Re: Problems resolving paths in copy's "tofile" when combining multiple properties

2010-03-03 Thread Antoine Levy Lambert
Hello Oliver, on mac, because mac is a UNIX like system, gets expanded to /acme/servlet/messages.properties because of the leading slash, ant thinks that /acme/servlet/messages.properties is an absolute path and should not be resolved. In fact your error is to use the attribute location ins

Re: Problems resolving paths in copy's "tofile" when combining multiple properties

2010-03-03 Thread Oliver Schrenk
I solved my problem by using two properties, one for "file" and one for "tofile" I wonder though why the original approach works on Mac platform but not on windows. There are different two behaviours: 1.MAC: multiple properties in "tofile" are first resolved, concatenated and then converted to

Re: Problems resolving paths in copy's "tofile" when combining multiple properties

2010-03-03 Thread Antoine Levy Lambert
Oliver Schrenk wrote: Here is an excerpt from the build file: ... Is this a known issue, expected behavior or just bland misuse of properties on my part? change just this line when you use the idiom, the property is converted to an absolute path. ${classes} is a

Problems resolving paths in copy's "tofile" when combining multiple properties

2010-03-03 Thread Oliver Schrenk
Hi, I use an Ant script that shows different behavior on the Mac and Windows platform. Both Ant are used from within Eclipse Mac: Eclipse 3.5 (Build-id, 20090621-0832) with Ant 1.7.1.v20090120-1145 Windows: Eclipse 3.5 (Build id: 20100218-1602) with Ant 1.7.1.v20090120-1145 In particular it fail