> From: steve morin [mailto:[EMAIL PROTECTED] > > 1st usage convenience.. > A person that often uses a different build file could use a shell > script that calls ant using a different default for convenience. > > #!/bin/sh > ant -df config.xml "$@" > > or > alias cfg="ant -df config.xml"
No different than -f then. Even when using the hard-coded -f from an alias, you can still specify another one on the command line, since the last one wins, so really it doesn't bring anything. > 2nd usage dynamic change of ant task default target. Just use a property you can override from the command line, and always set in your wrapper script or alias. > 3rd usage dynamic change of subant task calls Ditto. I thus don't think it's a useful addition, since all scenarios can be easily achieved right now, in the usual Ant way. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
