I don't know how hard it would be, but I miss the possibility to run Gradle in a different JRE when configuring a Gradle Build launch configuration, just like it is possible with an Ant Build.
- the possibility to specify the JRE to use (see "JRE" tab of an Ant Build launch configuration)
- the possibility to compose the classpath for the Gradle build script (see "Classpath" tab of an Ant Build launch configuration)
- (most important) the possibility to set environment variables (see "Environment" tab of an Ant Build launch configuration) to be made available to Gradle when running the build script
The last thing would be extremely useful to me: in fact, right now the Gradle daemon says that I have no JAVA_HOME set (because I haven't this environment variable set at the OS level) so if I run a Gradle task that needs to compile Java code from Eclipse, I get an error because a JDK cannot be found. So, I'm forced to set this environment variable at the OS level or at least to make it available to the whole Eclipse IDE, with possible side effects on other components that may use that environment variable value.