Stephan, I think I found what I think was the problem:
If I say: ant -Dtest clean It will execute the default target. If I say: ant -Dtest=true clean it executes the clean target. I just wanted the variable to be defined, did not care for any especific since I can not test it anyway. 8-P Is this the expected behaviour? I would have thought that "test" should be defined as nothing (empty string) on the first case. I just tested it with the build file for ANT itself. With respect to the exception, our current production is a little OLD and in that version any parsing error finished complaining about modern compiler not being there and a stack trace. The current CVS tree fixed that. Thanks in advance, Jose Alberto > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 18, 2000 12:05 AM > To: [EMAIL PROTECTED] > Subject: Re: Apparent bug on ANT > > > >>>>> "JAF" == Jose Alberto Fernandez <[EMAIL PROTECTED]> writes: > > JAF> But if I call ----> ant -Dprop=value target ant will execute the > JAF> default target for the build. Instead of "target". > > Could send a little exampe build file with example commandlines? I've > been using both versions of > > ant run.single.test -Dtestcase=org.apache.tools.ant.types.PathTest > ant -Dtestcase=org.apache.tools.ant.types.PathTest run.single.test > > on Ant's own buildfile without any problems (Linux and latest CVS > version of Ant). > > JAF> Another funny thing I have noticed is that everytime my build > JAF> fails I will get an stack trace from ANT is this the spected > JAF> behaviour? > > No - and I don't see this. Looks as if something very strange is > happening (like Diane once had <echo> print its message twice > everytime). > > Stefan >
