Ken got my point! Tks for that :-) Peter, the Wrapper did the trick for me. The variables are set on a project-basis and that's what I want. Otherwise, I'd just use a script to set the env variables and would call it the same way as the gradlew script.
Now, an improvement to Gradle would be for it to "include" Wrapper, so that instead of calling this "gradlew" script, we would keep with the "gradle" command, which would detect the presence of Wrapper configuration and would set the VM options and spawn a new gradle instance to run the specified tasks. Cheers, PP On Wed, Feb 9, 2011 at 2:48 PM, Peter Niederwieser <[email protected]>wrote: > > > kensipe wrote: > > > > I think Paulo is saying that he would rather not set GRADLE_OPTS (which > is > > typically a sys wide env var)... he would rather set VM configs etc., on > a > > project by project basis. With GRADLE_OPTS he is forced to either set > the > > values system wide... or create a BASH script to set it per project. > > > > Oh I see. When we were discussing ways to improve the Gradle Wrapper in > this > thread, we were always referring to a project-specific solution. After all, > that's what the Wrapper is all about. The only question is how to merge > user-specific and project-specific settings. > > -- > 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/Setting-GRADLE-OPTS-in-gradle-properties-tp3364427p3377683.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 > > > -- Paulo Pires
