Allow additional variables in properties file

[GoogleCodeExporter]

This is an issue due to an upgrade from 3.0.2 to 3.0.6.

On my local machine I have a few databases for each project.  e.g. A 
development DB (foo), an integration test DB (foo-test), and a functional test 
DB (foo-functional.  I use the script feature to generate scripts for my 
production DBAs.  Because of the external hand-off to users that use the sa 
account or their own login to run the scripts, I need to prefix each script 
with a USE foo command to set the correct database context.
The trouble is that I can't hard-code the database name in that USE command, 
because I'm using more than one database name.  So I need a variable name for 
the database.

I was using the bug that was fixed in Issue #356 as a feature to set a property 
in each properties file. e.g. in development.properties I added:
database=foo

and then referenced that property in the scripts - e.g. USE ${database}

But this doesn't work since the fix for that bug.  Do you have any suggested 
solutions for this situation?  e.g. Would it be acceptable to allow a couple 
more variables in the properties files, or allow specially prefixed variables?  

Thanks,
Dan

Original issue reported on code.google.com by d...@dantanner.com on 25 Sep 2012 at 4:03