sorry, my email has been off for a few days (moving to a new building). the difference is that the -D mechanism requires a property name. i need to just be able to pass in command-line arguments, one after the other, without having to explicitly set each one as a property.
i submitted a patch that does this, but it's entirely possible that this isn't a feature anybody cares about, of course. -- Salman Halim Advisory Software Engineer, HP Bluestone Quidquid latine dictum sit, altum viditur. -----Original Message----- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Monday, April 09, 2001 11:43 PM To: [EMAIL PROTECTED] Subject: Re: command-line arguments On a semi-related note, how about a way to unset them in a way that still counts as a User override (so they can't be un-undefined in the build file)? d On Wed, 4 Apr 2001 11:05:40 -0400 , Jesse Tilly wrote: >Since this is already possible using -D, what's the difference? > >JT > >-----Original Message----- >From: Halim, Salman [mailto:[EMAIL PROTECTED] >Sent: Wednesday, April 04, 2001 11:05 AM >To: '[EMAIL PROTECTED]' >Subject: command-line arguments > > >hi, > >i have started using ant quite recently -- we're thinking of using its >platform independent features to replace batch files and shell scripts (in >part) rather than as an installation tool. toward that end, i wanted to >modify the org.apache.tools.ant.Main class to set all command-line >parameters following a lone hyphen (-) as properties (of the form 'arg1', >'arg2' etc.). > >any thoughts on this? good idea/bad idea/been done etc.? > >thank you in advance!
