Paulo Pires wrote: > > 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. >
Which benefits do you hope to gain from that? Is it just "gradle" vs. "gradlew" or something else? The main reason for using the wrapper is to make it unnecessary to manually install (and update) Gradle. But without a Gradle installation, there won't be a "gradle" script. I think of "gradle" as a user-specific (and user-provided) installation, and "gradlew" as a project-specific (and automatically provided) installation. Not sure if we should start to mix between the two (like having "gradle" use the wrapper settings). I'd rather try to make "gradlew" more convenient to use. The only inconvenience I'm aware of is that you can't call "gradlew" by its simple name from a subproject directory. But this could be solved fairly easily. Anything else you don't like about "gradlew"? -- 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-tp3364427p3379426.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
