On 03/08/2011, at 11:13 PM, jstuyts wrote: > > Luke Stephens wrote: >> >> 2. As I posted in another post, there can be huge environment based issues >> (gradle run inside of eclipse runs totally differently than gradle run at >> the command line) >> > > I think this is a very important aspect of a build tool, which unfortunately > does not seem to get enough attention right from the start of the > implementation of a new build tool. > > I am currently working on a very thin wrapper around Gradle to ensure that > exactly the same build environment is used on every machine on which the > code is built. This means making sure the correct JDK, Gradle, Ant library, > Jython, ... versions are used for a project/branch, and no > environment-specific things that may influence the build are picked up by > any of the tools.
You might think about using the wrapper for this. This would lock down the Gradle version. You could tweak the wrapper script to point to the appropriate JDK. For everything else you can declare the appropriate versions in the build script. By doing this, the Eclipse integration (and the upcoming IDEA integration) will pick up exactly the same version Gradle, and everything declared in the build script. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
