Gradle Release Notes
Version 0.9.2
- New and Noteworthy
- Migrating from 0.9.1
- Fixed Jira Issues
New and Noteworthy
This is mainly a bug-fix release. However, there are a couple of minor improvements:
Simpler installation on Windows
The gradle.bat script no longer requires that you set the JAVA_HOME environment variable. It will simply pick up the version of Java from your PATH. You can still set JAVA_HOME if you prefer.
This behaviour has always been available in the gradle UNIX script.
Improvements to DSL
There are some changes to the Gradle build language to simplify writing rules in your build. Here's an example which changes the baseName for all Zip tasks:
| 0.9 |
0.9.2 |
tasks.withType(Zip).allObjects { zip ->
zip.baseName = "gradle-${zip.name}"
}
|
tasks.withType(Zip) {
baseName = "gradle-${name}"
}
|
There are a number of similar convenience methods available on {{DomainObjectCollection}}, which is used in many places in the build language. For more details see the
API.
0.9.2 Breaking Changes
- Command-line changes
- IDEA and Eclipse plugin changes
- Deprecations
Command-line changes
- Environment variable GRADLE_HOME removed. The gradle and gradlew commands no longer support the GRADLE_HOME environment variable.
- Command-line options \-A and \--dep-tasks removed.
IDEA and Eclipse plugin changes
- The IDEA and Eclipse plugins now configure the IDEs to compile classes into their respective default locations, rather than attempting to share the Gradle classes directory.
- The IDEA and Eclipse plugins no longer merge any existing classpath defined in the IDE configuration files with the classpaths defined in the Gradle build. The plugins will always replace the existing classpath with that defined in the Gradle build. You can reproduce the old behaviour using a combination of beforeConfigured and whenConfigured.
Deprecations
- Deprecated DomainObjectCollection.allObjects(), TaskCollection.allTasks() and PluginCollection.allPlugins(). These are replaced by DomainObjectCollection.all().