It is now much easier to define an Ivy repository. Here's an example:
Defining an Ivy repository
repositories {
ivy {
name = 'libs'
userName = 'some-user'
password = 'some-password'
artifactPattern 'http://myrepo.com/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]'
}
}
Compare this with how you used to define an Ivy repository:
The old way
repositories {
org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials('Some Realm', 'myrepo.com', 'some-user', 'some-password')
add(new org.apache.ivy.plugins.resolver.URLResolver()) {
name = 'libs'
addArtifactPattern('http://myrepo.com/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]')
}
}
Under the covers, Gradle will choose the appropriate repository implementation based on the URL patterns you have supplied. In particular, Gradle now works better for HTTP and HTTPS repositories:
There is now an easier way to query for all the source directories of a source set. The allSource, allJava, allGroovy and allScala properties now have a srcDirs property. Here's an example:
sourceSets.main.allSource.srcDirs.each { dir -> println "src dir: $dir" }
Previously, you has to manually merge the source directories from the java, resources, groovy and scala source.
A new API is available to make it easier to integrate Gradle with tools such as IDEs, CI servers and other tools. The goal of this API is to provide a way to execute Gradle builds, and to query information about them, in a way that is independent of Gradle version. If you maintain some integration with Gradle, you should consider switching to use the tooling API.
Gradle 1.0-milestone-3 Breaking Changes
Have a look at Gradle 1.0-milestone-3 Release Notes for more information about the new features in this release
The GradleLauncher API has been deprecated. This class has been replaced by the tooling API for launching builds, and will be removed in the very near future.
See ProjectConnection for details, and the samples in $gradleHome/samples/toolingApi.
The open API has been deprecated. This includes usages of org.gradle.openapi.external.ui.UIFactory and org.gradle.openapi.external.runner.GradleRunnerFactory. This API has been replaced by the tooling API for launching and querying builds, and will be removed in a future release of Gradle.
See ProjectConnection for details, and the samples in $gradleHome/samples/toolingApi.