Gradle 1.0-milestone-6 released

(Adam Murdoch) #1

The Gradle team is pleased to announce the release of Gradle 1.0-milestone-6.

This release contains some nice new features, some major performance improvements, and plenty of bug fixes. You can read more in the release notes.

Please make sure you read the migration guide to find out about known issues and breaking changes in this release.

Download this release from the usual spot at or point your wrapper at

(Pranav K Varshney) #2

Running under Milestone 6 gives me the following error -

Caused by: org.gradle.api.internal.MissingMethodException: Could not find method externalDependencis() for arguments [build_7gslcdpg1pe0grk29isjrlf8sc$_run_closure1@315068] on root project 'pgutils'
        at org.gradle.api.internal.AbstractDynamicObject.methodMissingException(AbstractDynamicObjet.ava:60)
        at org.gradle.api.internal.AbstractDynamicObject.invokeMethod(
        at org.gradle.api.internal.CompositeDynamicObject.invokeMethod(
        at org.gradle.api.internal.project.DefaultProject_Decorated.invokeMethod(UnknownSource)
        at org.gradle.groovy.scripts.BasicScript.methodMissing(BasicScript.groovy:72)
        at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$
        ... 30 more

The same used to work under M05


externalDependencies {
 compile name: 'log4j'
 compile name: 'spring_core'
 testCompile name: 'junit'


project.extensions.add("externalDependencies", new ExternalDependenciesExtension(project: project))

I could not find any solution under migration guide.

Regards, Pranav

(Peter Niederwieser) #3

The build script that generated above stack trace contains a typo. externalDependencis should be externalDependencies.

(Pranav K Varshney) #4

yes, stack trace is

Could not find method externalDependencies() for arguments ....

Thanks for correcting it :slight_smile:

(Peter Niederwieser) #5

Are you sure that it wasn’t a typo in your build script? I doubt that your problem is caused by switching to m6.

(Pranav K Varshney) #6

yes… there is no typo in my build script. Same script works well with m5.

(Peter Niederwieser) #7

Did you do a clean build after switching to m6?

(Pranav K Varshney) #8

Great … after deleting my .gradle/caches folder and clean build fixed the issue. No clue why? May be some classpath issue

In last 2 weeks I have worked on M4, M5 and M6 and I am seeing a great improvement. M6 is really fast.

(Peter Niederwieser) #9

A clean build is necessary after switching to another Gradle version. It’s a known limitation.

(Liyu Wang) #10

It seems the new release parse the dependencies different than the M5 release, here is the example:

run the projectReport for

dependencies.jbossasRemoteTestRuntime([group: ‘org.jboss.arquillian.container’, name: ‘arquillian-jbossas-remote-6’, version: ‘1.0.0.CR2’],

[group: ‘org.jboss.spec’, name: ‘jboss-javaee-6.0’, version: ‘1.0.0.Final’],

[group: ‘org.jboss.jbossas’, name: ‘jboss-as-profileservice-client’, version: ‘6.1.0.Final’])

got different results with M5 and M6.

(Peter Niederwieser) #11

Please open a new topic, and use a code tag to make the source code that you post easier to read.

(Mark Flacy) #12


Milestone-6 does not appear to handle proxy configuration the same way as milestone-5 did. We have projects that are able to connect to mavenCentral() via our proxy as configured in our file(s) when running milestone-5 that are unable to connect with milestone-6.

* Exception is:
org.gradle.api.internal.artifacts.ivyservice.ModuleVersionResolveException: Could not resolve group:bouncycastle, module:bcprov-jdk14, version:140.
Caused by: Connection timed out: connect
 at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(
 at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(
 at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(
 at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(
 at org.apache.commons.httpclient.HttpClient.executeMethod(
 at org.apache.commons.httpclient.HttpClient.executeMethod(
 at org.gradle.api.internal.artifacts.repositories.CommonsHttpClientBackedRepository$LazyResourceInvocationHandler.init(
 at org.gradle.api.internal.artifacts.repositories.CommonsHttpClientBackedRepository$LazyResourceInvocationHandler.invoke(
 ... 84 more

When run with the debug flag, I can see where the org.gradle.api.internal.artifacts.ivyservice.IvyLoggingAdaper class is reporting is setting http.proxyHost and http.proxyPort to the correct values, but the connection nonetheless fails.

(david koch) #13

I also faced this problem. Going through the company firewall is no issue with milestone-5 but milestone-6 doesn’t work with the proxy config in I do not use maven central but spring repositories.

(Peter Niederwieser) #14

It’s a known problem that has already been fixed for the upcoming milestone 7.