The Gradle Daemon is no longer considered experimental and is considered stable. See the user guide chapter on the Gradle Daemon for more information.
The new “Extra Properties” mechanism replaces “Dynamic Properties”. See the relevant section of the migration guide for more information.
We've shed some weight as we prepare for 1.0 final by removing some long deprecated items. The full list is in the migration guide.
The (Java) Compile task now uses Gradle's own compiler integration by default, rather than using the Ant javac task. In many cases, this already speeds up compilation today, and it will allow us to do further improvements in the future. When run in fork mode (compile.options.fork = true), Gradle's compiler configuration won't fork a new JVM for each compile task, but will try to reuse the same JVM as much as possible. This can result in a significant speedup (in particular for builds with many smaller projects) while still giving you all the advantages of forking (like advanced compiler configuration options). For the time being, you can still get back the Ant javac integration with compile.options.useAnt = true.
You can now pass Task outputs to the from method of copy or archive tasks. This adds an implicit dependency to the output producing task.
As a default, the evaluation of child projects depends on the evaluation of its parent projects. Changing this default behavior has been simplified:
It is now easier to work with executables that use shared libraries. The C++ plugins now add an installMain task, which creates a local development installation of the executable, that also includes the shared libraries that the executable requires at runtime. You can run the executable directly out of the installation, without needing to install shared libraries or to mess with platform-specific environment variables.
In previous versions, only builds executed with the Gradle daemon would honour the org.gradle.java.home and org.gradle.jvmargs properties. These properties are now honoured by non-daemon builds as well. In order to do this, Gradle needs to fork a new JVM if the launched build process does not satisfy these requirements.
In order to avoid the performance impact of Gradle launching a second JVM for every build execution, you can:
See Gradle 1.0-milestone-9 Migration Guide
|JIRA Issues (33 issues)|
|GRADLE-2158||Zip files created on Windows platform have zero FilePermission when unpacked with Gradle||René Gröschke||René Gröschke||Resolved||Fixed||Mar 07, 2012||Jan 04, 2013|
|GRADLE-2127||C++ plugin should provide support for mingw||Unassigned||Adam Murdoch||Resolved||Fixed||Feb 27, 2012||Jan 04, 2013|
|GRADLE-2126||Extraneous output prefix is seen on every line when output from gradlew on Unix is redirected to file||Unassigned||Gradle Forums||Resolved||Fixed||Feb 26, 2012||Jan 04, 2013|
|GRADLE-2120||ConfigureUtil.configureByMap does not work correctly with decorated objects (does not call methods with the given name)||Luke Daley||Luke Daley||Resolved||Fixed||Feb 22, 2012||Jan 04, 2013|
|GRADLE-2119||Cannot specify builtBy for artifact using map notation||Luke Daley||Luke Daley||Resolved||Fixed||Feb 22, 2012||Jan 04, 2013|
|GRADLE-2117||provide support for visual c++||Unassigned||Adam Murdoch||Resolved||Fixed||Feb 22, 2012||Jan 04, 2013|
|GRADLE-2116||provide c++ support on mac os x||Unassigned||Adam Murdoch||Resolved||Fixed||Feb 22, 2012||Jan 04, 2013|
|GRADLE-2108||cpp executable that links against shared libraries does not work if the shared libraries are moved from their link-time location||Unassigned||Adam Murdoch||Resolved||Fixed||Feb 15, 2012||Jan 04, 2013|
|GRADLE-2104||milestone-8 : jsch-0.1.42.jar missing, Ivy SFTPResolver can not be be used anymore||Unassigned||Gradle Forums||Resolved||Fixed||Feb 15, 2012||Jan 04, 2013|
|GRADLE-2102||Tooling API LongRunningOperation.setJavaHome() fails with NoClassDefFoundError||Szczepan Faber||Adam Murdoch||Resolved||Fixed||Feb 14, 2012||Jan 04, 2013|
|GRADLE-2099||Impossible to set the default character encoding when using the daemon||Luke Daley||Luke Daley||Resolved||Fixed||Feb 14, 2012||Jan 04, 2013|
|GRADLE-2081||warning emitted when compiling using openjdk 7||René Gröschke||Adam Murdoch||Resolved||Fixed||Feb 04, 2012||Jan 04, 2013|
|GRADLE-2079||Eclipse plugin generates invalid javadoc locations||Unassigned||Alex Romanyuk||Resolved||Fixed||Feb 03, 2012||Jan 04, 2013|
|GRADLE-2076||Artifact not found resolving dependencies with packaging/type "eclipse-plugin"||Daz DeBoer||Gradle Forums||Resolved||Fixed||Feb 01, 2012||Jan 04, 2013|
|GRADLE-2072||CopySpec.from <someTask>.outputs is silently ignored||Unassigned||Adam Murdoch||Resolved||Fixed||Jan 29, 2012||Jan 04, 2013|
|GRADLE-2068||archives built from configurations contain duplicate jars (M5->M6 regression)||Daz DeBoer||Szczepan Faber||Resolved||Fixed||Jan 25, 2012||Jan 04, 2013|
|GRADLE-2044||Cannot manually remove dependencies from milestone-8 cache structure||Daz DeBoer||Chris Beams||Resolved||Fixed||Jan 12, 2012||Jan 04, 2013|
|GRADLE-2038||Tar decompression should also understand .bz2 and .gz extensions||René Gröschke||Ben Jansen||Resolved||Fixed||Jan 09, 2012||Jan 04, 2013|
|GRADLE-2036||Excludes DSL needs some improvements (error on unknown keys, error if no valid keys)||Unassigned||Gradle Forums||Resolved||Fixed||Jan 06, 2012||Jan 04, 2013|
|GRADLE-2019||EAR plugin fails if JavaBasePlugin is applied before the EAR plugin (and JavaPlugin is not applied)||René Gröschke||Andrew Oberstar||Resolved||Fixed||Dec 30, 2011||Jan 04, 2013|
|GRADLE-1900||Apply the repo location from the maven config in mavenLocal()||Peter Niederwieser||Mike M.||Resolved||Fixed||Nov 08, 2011||Jan 04, 2013|
|GRADLE-1872||Regular use of eclipse tooling api leads to deprecation warnings||Luke Daley||Szczepan Faber||Resolved||Fixed||Oct 27, 2011||Jan 04, 2013|
|GRADLE-1857||source(someDir) is not adding the directory to the set of sources, instead is clobbering it||Unassigned||David Kowis||Resolved||Fixed||Oct 20, 2011||Jan 04, 2013|
|GRADLE-1771||Tooling API should start daemon with -client option (or at least provide a way to control options passed to daemon process)||Szczepan Faber||Kris De Volder||Resolved||Fixed||Aug 29, 2011||Jan 04, 2013|
|GRADLE-1680||Eclipse plugin generates incorrect path for library javadocs||Unassigned||Adam Murdoch||Resolved||Fixed||Jul 20, 2011||Jan 04, 2013|
|GRADLE-1618||file.encoding System property (and GRADLE_OPTS) not passed to Daemon||Luke Daley||David Fogel||Resolved||Fixed||Jun 15, 2011||Jan 04, 2013|
|GRADLE-1531||Compile seems to ignore options.encoding||Unassigned||Peter Rietzler||Resolved||Fixed||May 12, 2011||Jan 04, 2013|
|GRADLE-1483||Tasks of type JavaExec fails to honor inputs/outputs||Luke Daley||Magnus Rundberget||Resolved||Fixed||Apr 18, 2011||Jan 04, 2013|
|GRADLE-1381||The 'eclipse' task for Gradle's build is incredibly slow||Unassigned||Peter Niederwieser||Resolved||Fixed||Feb 07, 2011||Jan 04, 2013|
|GRADLE-1255||Exclude rule silently excludes everything if neither 'module' or 'group' specified||Unassigned||Adam Murdoch||Resolved||Fixed||Dec 15, 2010||Jan 04, 2013|
|GRADLE-1246||Fails silently when try to unzip non-existent file||Unassigned||Peter Bell||Resolved||Fixed||Dec 06, 2010||Jan 04, 2013|
|GRADLE-796||Copy task should preserve file permissions||Peter Niederwieser||Adam Murdoch||Resolved||Fixed||Jan 12, 2010||Jan 04, 2013|
|GRADLE-673||file permissions not preserved in Tar task||Peter Niederwieser||Philip Crotwell||Resolved||Fixed||Oct 02, 2009||Jan 04, 2013|