 | Have a look at Gradle 1.0-milestone-4 Release Notes for more information about the new features in this release |
Classpath changes
The Jars included in the Gradle distribution in $gradleHome/lib and $gradleHome/lib/plugins are no longer visible in the build script classpaths.
eclipse/idea plugin
Changes to the eclipse/idea plugin were necessary to accommodate the implementation of the Tooling API. Tooling API is necessary for very promising tools like the Eclipse STS gradle plugin.
Referring to the 'eclipse' and 'idea' tasks in gradle script is only possible via 'tasks'. Please use 'tasks.idea' or 'tasks.eclipse'. The other related tasks, like 'ideaProject', 'ideaModule', 'eclipseClasspath', etc. are left untouched (however, they have many methods & properties deprecated but those are not breaking changes).
eclipse WTP plugin
WTP generation was separated from the eclipse plugin. The new 'eclipse-wtp' plugin applies 'eclipse' plugin and also adds WTP-generation tasks.
New artifact cache location and layout
The artifact cache now lives under ~/.gradle/caches/artifacts and has a new layout. The old location ~/.gradle/cache is no longer used for anything and can be safely deleted.
API Changes
- Removed Configuration.publish(). There is no public replacement. You should use the Upload task type to publish a configuration to a set of repositories.
- Removed Project.createRepositoryHandler(). There is no public replacement.
AbstractTask.execute() has been made final
To prevent users accidentally overriding this very important method in their own tasks, it has been made final.
For Gradle developers
Debugging gradle builds from IDEA (advanced)
This information is useful for devs who have gradle project itself set up in IntelliJ (e.g. contributors, core devs) and they debug gradle builds from IDEA. See the updated wiki page on how to run gradle builds from IDEA.