I do this and have been very happy with it. We have a directory stucture
that is set up in our source control system (StarTeam) and using the
build.bat, we are able to override the default paths for consultants who
have their source and tools set up differently.
I use an ant.properties file to set up all my properties and override the
ones I want in my build.bat by sending them as parameters. I've included
my build.bat, build.xml, and ant.properties to illustrate. Get back to me
if you have questions.
(See attached file: build.bat)(See attached file: build.xml)(See attached
file: ant.properties)
Andy
****************************
Andrew Goodnough
Dana Commercial Credit
Programmer
(419) 891-2065
"Halim,
Salman" To: "'[EMAIL PROTECTED]'"
<salman@Blues <[EMAIL PROTECTED]>
tone.com> cc:
Subject: command-line arguments
04/04/2001
01:46 PM
Please
respond to
ant-user
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!
--
Salman Halim
Advisory Software Engineer, HP Bluestone
Quidquid latine dictum sit, altum viditur.
build.bat
build.xml
ant.properties
