On Jul 16, 2009, at 4:00 PM, Jason Porter wrote:
On Wed, Jul 15, 2009 at 14:53, Adam Murdoch<[email protected]>
wrote:
Jason Porter wrote:
It looks like the gradle.properties in USERHOME/.gradle is it, but
how
does this work if you have multiple projects being built with
Gradle?
Is there a special prefix for the keys to assign it to a particular
project?
You can put a gradle.properties file in the project directory of a
project.
These properties are applied to the project, and inherited by all its
sub-projects.
Also, you can use code to do this if the build-in stuff doesn't
work. For
example:
Properties props = new Properties()
file('my-properties.properties').withInputStream { props.load(it) }
props.each { String name, value -> project.setProperty(name, value) }
That's a lot of code for something so simple. I was mostly looking at
this for building in different environments, local, dev, acceptance,
prod, etc. If you loaded up properties via the AntBuilder, would they
be available to Gradle?
No.
That would be simpler solution until (if?)
Gradle has a simpler means (maybe wrap it all up into a project method
called addProperties or something like that, it could have a few
overloads: String, Properties, File, Map, etc)
We definitely want to support environment specific configuration in
the future. We also want to support configuration scripts, not just
property files. We just haven't get around to implement this.
Could you file a Jira?
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
