You could also have a set of properties files and load up the appropriate one based on the "profile" if you start having a lot of things that need to be changed.
On Mon, Feb 7, 2011 at 14:58, Peter Niederwieser <[email protected]> wrote: > > > Neil Chaudhuri wrote: >> >> That worked for me...except I had to explicitly state the project object. >> > > Depends on where you are doing this. At the top level of the script it isn't > necessary, but within a task (to give an example) it is. > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Creator, Spock Framework > http://spockframework.org > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Simulating-Maven-Profiles-tp3374782p3374996.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
