. That way, all a user has to do
> is copy build.properties.template to build.properties and edit the
> values they want to change.
>
> Remember that will not fail if the file
> mentioned doesn't exist and that you can override
> properties values set in your build.xml fi
ent, there generally is a way to access that argument inside the
program to which it is passed. It just seems surprisingly non-intuitive that
the -propertyfile is not accessible inside the script itself.
I'd certainly be interested if anyone can satisfy this curiosity.
supareno wrote:
>
&g
When I run ant as follows:
ant -propertyfile
e.g.
ant -propertyfile myProps.properties test
how do I find out the the name of the properties file that the user passed
in the command line argument. So my ant script looks like:
Essentially, is there a place/property where the comma
