On 8 May 2014 at 11:23:00 am, Adam Murdoch ([email protected]) wrote:
On 8 May 2014, at 1:50 am, Daz DeBoer <[email protected]> wrote: G'day It appears that a few regressions slipped into the 1.12 release. Here's the list of possible regressions that I'm aware of: GRADLE-3076: Gradle 1.12-rc-2 fails with UnsatisfiedLinkError on some Linux versions This was reported in 1.12-rc-2. Was it fixed for 1.12? No. It happens on old Linux distributions (released earlier than 2005 or so) and you can workaround with -Dorg.gradle.native=false so it has a somewhat low priority relative to other things. I’ll try to do a fix for 2.0. GRADLE-3079: Method in build.gradle not available in imported scripts (regression in 1.12) This is the classloader regression in "apply from" that Luke is working on GRADLE-3080: gradle 1.12 now downloads snapshots when I apply a version range Not sure if this has been verified, but I suspect it's due to the changes to version listing that I did It does indeed do this now, for Maven repositories. For Ivy repositories it has always resolved to snapshots. Strictly speaking, the new behaviour is more correct, so we may not change this back. Let’s see. GRADLE-3081: gradle 1.12 tries to resolve custom packaging with .jar extension Not sure if this has been investigated/verified, but it sounds credible This was broken in 1.12 but is fixed again now. GRADLE-3082: "class loader scope is locked" error when building GroovyFX with Gradle 1.12 This has been verified by Peter @Luke can you take a look at this one? Yes, doing so today. — Luke Daley Gradleware Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com
