Gradle 0.5.1 is released.
This is mostly a bug fix release. We recommend everybody to upgrade as
the caching of the build script is now more reliable, which is
something that affects every user.
- The build script cache is now automatically rebuild if you switch to
a new version of Gradle. Gradle has also switched from a timestamp to
a MD5 based cache invalidation schema.
- It is now possible to specify arbitrary arguments to pass to the
javac compiler.
- It is now also easier to work with jars that don't have a version. A
version is now optional, if you use the FlatDirResolver.
- See also the incompatibility note at the end of the mail.
The size of the gradle-all distribution has decreased for 4MB, as the
samples jars are no longer part of the distribution, but are
downloaded from a repository on demand. For a similar reason, the size
of the source distribution has decreased from 25 MB to 1.4 MB.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
Release Notes - Gradle - Version 0.5.1
** Bug
* [GRADLE-311] - Cached build script is not updated when build
file is reverted
* [GRADLE-318] - Build fails when buildSrc directory contains
java source files and does not contain a build.gradle file. The build
fails also for Groovy projects that have no java code.
* [GRADLE-319] - Gradle fails with NPE for a build/settings
script which does not contain any executable code
* [GRADLE-330] - Setting archivesBaseName has no effect on the
default archive name, if usePlugin('java') has been called before.
* [GRADLE-341] - stdout capture discards empty lines
* [GRADLE-343] - Jetty plugin fails to start with 2.5 deployment
descriptor
** Improvement
* [GRADLE-186] - Invalidate cache if a new version of Gradle is
used.
* [GRADLE-334] - Make specifying the version optional for flat
dir resolver.
** New Feature
* [GRADLE-342] - Compile task needs to support the compilerarg
parameters
** Incompatibilities to 0.5
There is a slight incompatibility which should only effect some rare
cases. To fix GRADLE-330, the archiveTask has now an additional
property called appendix which is part of the generated jar name.
Before this fix, the baseName and the appendix of the arguments of the
archive methods was added and assigned to the baseName of the archive
task. Now those arguments are assigned to the respective archive task
properties.
Example:
archivesBaseName = 'gradle'
libs {
// NO INCOMPATIBILITIES
// Creates and archive task with the baseName 'gradle' and the
appendix 'all'. The name of the generated archive is gradle-all-
<version>.jar
// Before 0.5.1: Creates and archive task with the baseName 'gradle-
all'. The name of the generated archive is the same as above
jar(appendix: 'all')
// NO INCOMPATIBILITIES
// Creates and archive task with the baseName 'myGradle' and the
appendix 'all'. The name of the generated archive is myGradle-all-
<version>.jar
// Before 0.5.1: Creates and archive task with the baseName 'myGradle-
all'. The name of the generated archive is the same as above
jar(baseName: 'myGradle', appendix: 'all')
// INCOMPATIBILITIES occur, if the appendix argument in the archive
method is set and the baseName of the created archive task is
overwritten later on.
// In 0.5.1 the following lead to an archive task with the baseName
'newGradle' and the appendix 'all'. The name of the generated archive is
// newGradle-all-<version>.jar
// Before 0.5.1: The archive task has the baseName 'newGrade'. The
name of the generated archive is newGradle-<version>.jar
jar(appendix: 'all')
archive_gradle_all_jar.baseName = 'newGradle'
}
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
