Gradle 2.1-rc-3 is now available for testing

The Gradle team is pleased to announce that the third release candidate for Gradle 2.1 is now available.

This addresses the following issues identified with 2.1-rc-2:

  • GRADLE-3153 - problems loading ivy metadata from dependency cache

Download links and release notes can be found as always at http://gradle.org/release-candidate.

Please try Gradle 2.1-rc-3 with your projects and let us know your experiences.

Everything fine with my 3 projects.

With gradle-2.1-rc-3 (also gradle-2.1-rc-2) build fails as follows:

:webapp:installCompass
ERROR:
Could not find a valid gem 'compass' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - Errno::ECONNREFUSED: Connection refused - Connection refused (https://rubygems.org/latest_specs.4.8.gz)
:webapp:installCompass FAILED
  FAILURE: Build failed with an exception.
  * What went wrong:
Execution failed for task ':webapp:installCompass'.
> Process 'command '/usr/lib64/jvm/java-1.7.0-openjdk-1.7.0/bin/java'' finished with non-zero exit value 2
  * Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
  BUILD FAILED

This does not occur with gradle-2.1-rc-1 or gradle-1.12.

Using --info option with gradle-2.1-rc-3 I see

Executing task ':webapp:installCompass' (up-to-date check took 0.075 secs) due to:
  No history is available.
Starting process 'command '/usr/lib64/jvm/java-1.7.0-openjdk-1.7.0/bin/java''. Working directory: /home/helge/mvc5/webapp Command: /usr/lib64/jvm/java-1.7.0-openjdk-1.7.0/bin/java -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /home/helge/.gradle/caches/modules-2/files-2.1/org.jruby/jruby-complete/1.7.10/f74a8b29da11e2ea430a1d1d92b72d424f7ee311/jruby-complete-1.7.10.jar org.jruby.Main -X-C -S gem install -i /home/helge/mvc5/webapp/.jruby/gems --no-rdoc --no-ri compass
Successfully started process 'command '/usr/lib64/jvm/java-1.7.0-openjdk-1.7.0/bin/java''
ERROR:
Could not find a valid gem 'compass' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - Errno::ECONNREFUSED: Connection refused - Connection refused (https://rubygems.org/latest_specs.4.8.gz)
:webapp:installCompass FAILED

With gradle-2.1-rc-1 all is well:

:webapp:installCompass (Thread[Daemon Thread 3,5,main]) started.
:webapp:installCompass
Skipping task ':webapp:installCompass' as it is up-to-date (took 0.075 secs).
:webapp:installCompass UP-TO-DATE
:webapp:installCompass (Thread[Daemon Thread 3,5,main]) completed. Took 0.078 secs.

This occurs reliably if I switch back and forth between rc-1 and rc-3. It appears to me that gradle-2.1-rc-3 does not want to believe that installCompass is UP-TO-DATE.

Well I moved back to gradle-compass:1.0.9 from 1.0.10 and the error is gone. Maybe some anomaly in my cache.

With 2.1-rc-3 I get problems resolving dependencies on our internal Artifactory server.

Caused by: java.text.ParseException: xml parsing: ivy.xml:10:77: cvc-complex-type.3.2.2: Attribute ‘classifier’ is not allowed to appear in element ‘artifact’. in file:/C:/Users/swp/.gradle/caches/modules-2/metadata-2.13/descriptors/my.company.jre/jre-wix/1.7.0_51/216e09171911559d4aa0ec699335c8fd/ivy.xml

at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.IvyXmlModuleDescriptorParser$AbstractParser.checkErrors(IvyXmlModuleDescriptorParser.java:155)

at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.IvyXmlModuleDescriptorParser$Parser.parse(IvyXmlModuleDescriptorParser.java:495)

at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.IvyXmlModuleDescriptorParser.doParseDescriptorWithProvidedParser(IvyXmlModuleDescriptorParser.java:97)

at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.IvyXmlModuleDescriptorParser.doParseDescriptor(IvyXmlModuleDescriptorParser.java:88)

at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.parser.AbstractModuleDescriptorParser.parseDescriptor(AbstractModuleDescriptorParser.java:44)

… 118 more

Thanks for reporting, you encountered https://issues.gradle.org/browse/GRADLE-3161. We are aware of that issue, a fix has been already applied and there will be another RC promoted soon.