Regression list for 1.12

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Regression list for 1.12

Daz DeBoer-2
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?
  • 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
  • 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
  • GRADLE-3082: "class loader scope is locked" error when building GroovyFX with Gradle 1.12
    • This has been verified by Peter
I guess we need to decide which of these should be fixed for 2.0, and make fixing them a priority. We should also update the "Affects Version" for any that are verified regressions.

Regarding the underlying issue of regressions: the RC phase for 1.12 was over 2 weeks long, so perhaps the reason these weren't caught is that there's little pressure for people to try out the RC, particular when we release so frequently. I'm not sure there's any "solution" to this, but some things that might help are:
  • Release more frequently (4-6 weeks), so that regressions don't cause too much pain and each release contains less stuff
  • Make it easy for users to configure a build to always run with the latest gradle. Something like "latest.rc" in the wrapper config, or a command-line override. That way, more people might setup CI jobs that would catch regressions in the RC phase.
--
Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Steve Ebersole
On the selfish side, personally I'd say that I have no compelling reason to upgrade (heck Hibernate is still using 1.9) because none of the bugs/requests I have reported have been addressed.  These range from LONG standing, simple ones like standardized "provided" configuration support to more complex ones.

Given that I would actually want to help (either because an RC includes fixes for one or more of my reports, or because I am a good citizen) both of your suggestions are good.  Out of curiosity, why limit latest to just rc?


On Wed, May 7, 2014 at 10:50 AM, Daz DeBoer <[hidden email]> 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?
  • 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
  • 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
  • GRADLE-3082: "class loader scope is locked" error when building GroovyFX with Gradle 1.12
    • This has been verified by Peter
I guess we need to decide which of these should be fixed for 2.0, and make fixing them a priority. We should also update the "Affects Version" for any that are verified regressions.

Regarding the underlying issue of regressions: the RC phase for 1.12 was over 2 weeks long, so perhaps the reason these weren't caught is that there's little pressure for people to try out the RC, particular when we release so frequently. I'm not sure there's any "solution" to this, but some things that might help are:
  • Release more frequently (4-6 weeks), so that regressions don't cause too much pain and each release contains less stuff
  • Make it easy for users to configure a build to always run with the latest gradle. Something like "latest.rc" in the wrapper config, or a command-line override. That way, more people might setup CI jobs that would catch regressions in the RC phase.
--

Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

casey.mcginty@gmail.com
My two cents also. Right now the gradle-js-plugin is broken for 1.11 and 1.12, so this is preventing us from trying out any newer releases. There is an open pull request with the fix, but it is not merged yet.

- Casey McGinty


On Wed, May 7, 2014 at 6:09 AM, Steve Ebersole [via Gradle] <[hidden email]> wrote:
On the selfish side, personally I'd say that I have no compelling reason to upgrade (heck Hibernate is still using 1.9) because none of the bugs/requests I have reported have been addressed.  These range from LONG standing, simple ones like standardized "provided" configuration support to more complex ones.

Given that I would actually want to help (either because an RC includes fixes for one or more of my reports, or because I am a good citizen) both of your suggestions are good.  Out of curiosity, why limit latest to just rc?


On Wed, May 7, 2014 at 10:50 AM, Daz DeBoer <[hidden email]> 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?
  • 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
  • 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
  • GRADLE-3082: "class loader scope is locked" error when building GroovyFX with Gradle 1.12
    • This has been verified by Peter
I guess we need to decide which of these should be fixed for 2.0, and make fixing them a priority. We should also update the "Affects Version" for any that are verified regressions.

Regarding the underlying issue of regressions: the RC phase for 1.12 was over 2 weeks long, so perhaps the reason these weren't caught is that there's little pressure for people to try out the RC, particular when we release so frequently. I'm not sure there's any "solution" to this, but some things that might help are:
  • Release more frequently (4-6 weeks), so that regressions don't cause too much pain and each release contains less stuff
  • Make it easy for users to configure a build to always run with the latest gradle. Something like "latest.rc" in the wrapper config, or a command-line override. That way, more people might setup CI jobs that would catch regressions in the RC phase.
--




If you reply to this email, your message will be added to the discussion below:
http://gradle.1045684.n5.nabble.com/Regression-list-for-1-12-tp5712639p5712640.html
To start a new topic under gradle-dev, email [hidden email]
To unsubscribe from gradle-dev, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Luke Daley-2
In reply to this post by Steve Ebersole


On 8 May 2014 at 2:08:56 am, Steve Ebersole ([hidden email]) wrote:

On the selfish side, personally I'd say that I have no compelling reason to upgrade (heck Hibernate is still using 1.9) because none of the bugs/requests I have reported have been addressed.  These range from LONG standing, simple ones like standardized "provided" configuration support to more complex ones.

Given that I would actually want to help (either because an RC includes fixes for one or more of my reports, or because I am a good citizen) both of your suggestions are good.  Out of curiosity, why limit latest to just rc?

These are just the regressions from the 1.12 release, nothing else.

Regressions always have the highest priority.

On Wed, May 7, 2014 at 10:50 AM, Daz DeBoer <[hidden email]> 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?
  • 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
  • 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
  • GRADLE-3082: "class loader scope is locked" error when building GroovyFX with Gradle 1.12
    • This has been verified by Peter
I guess we need to decide which of these should be fixed for 2.0, and make fixing them a priority. We should also update the "Affects Version" for any that are verified regressions.

Regarding the underlying issue of regressions: the RC phase for 1.12 was over 2 weeks long, so perhaps the reason these weren't caught is that there's little pressure for people to try out the RC, particular when we release so frequently. I'm not sure there's any "solution" to this, but some things that might help are:
  • Release more frequently (4-6 weeks), so that regressions don't cause too much pain and each release contains less stuff
  • Make it easy for users to configure a build to always run with the latest gradle. Something like "latest.rc" in the wrapper config, or a command-line override. That way, more people might setup CI jobs that would catch regressions in the RC phase.
--


— 

Luke Daley
Gradleware
Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com
Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Adam Murdoch
In reply to this post by Daz DeBoer-2

On 8 May 2014, at 1:50 am, Daz DeBoer <[hidden email]> 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?


--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com

Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com

Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Luke Daley-2


On 8 May 2014 at 11:23:00 am, Adam Murdoch ([hidden email]) wrote:


On 8 May 2014, at 1:50 am, Daz DeBoer <[hidden email]> 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
Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Russel Winder-3
In reply to this post by Adam Murdoch
On Thu, 2014-05-08 at 11:21 +1000, Adam Murdoch wrote:
[…]
> > 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?

This is also a problem for GPars as well as GroovyFX. Both projects must
therefore stay with 1.11 until this is fixed.

--
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[hidden email]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Luke Daley-2


On 8 May 2014 at 5:03:00 pm, Russel Winder ([hidden email]) wrote:

On Thu, 2014-05-08 at 11:21 +1000, Adam Murdoch wrote: 
[…] 
> > 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? 

This is also a problem for GPars as well as GroovyFX. Both projects must 
therefore stay with 1.11 until this is fixed. 

Workaround is explained on the original thread: http://forums.gradle.org/gradle/topics/groovyfx_build_fails_with_gradle_1_12_but_succeeds_with_1_11


— 

Luke Daley
Gradleware
Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com
Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Hans Dockter-2
In reply to this post by Steve Ebersole
Hi Steve,

On Wed, May 7, 2014 at 6:08 PM, Steve Ebersole <[hidden email]> wrote:
On the selfish side, personally I'd say that I have no compelling reason to upgrade (heck Hibernate is still using 1.9) because none of the bugs/requests I have reported have been addressed.  These range from LONG standing, simple ones like standardized "provided" configuration support

we are finally have started work on the foundation we need to solve this the way we want to solve it. With hindsight we should have provided a standardized provided configuration as a workaround for the time (i.e. years) being :) Now we just do it properly.

Hans
 
to more complex ones.

Given that I would actually want to help (either because an RC includes fixes for one or more of my reports, or because I am a good citizen) both of your suggestions are good.  Out of curiosity, why limit latest to just rc?


On Wed, May 7, 2014 at 10:50 AM, Daz DeBoer <[hidden email]> 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?
  • 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
  • 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
  • GRADLE-3082: "class loader scope is locked" error when building GroovyFX with Gradle 1.12
    • This has been verified by Peter
I guess we need to decide which of these should be fixed for 2.0, and make fixing them a priority. We should also update the "Affects Version" for any that are verified regressions.

Regarding the underlying issue of regressions: the RC phase for 1.12 was over 2 weeks long, so perhaps the reason these weren't caught is that there's little pressure for people to try out the RC, particular when we release so frequently. I'm not sure there's any "solution" to this, but some things that might help are:
  • Release more frequently (4-6 weeks), so that regressions don't cause too much pain and each release contains less stuff
  • Make it easy for users to configure a build to always run with the latest gradle. Something like "latest.rc" in the wrapper config, or a command-line override. That way, more people might setup CI jobs that would catch regressions in the RC phase.
--


Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Russel Winder-3
In reply to this post by Luke Daley-2
On Thu, 2014-05-08 at 17:36 +1000, Luke Daley wrote:

>
> On 8 May 2014 at 5:03:00 pm, Russel Winder ([hidden email]) wrote:
>
> On Thu, 2014-05-08 at 11:21 +1000, Adam Murdoch wrote:
> […]
> > > 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?
>
> This is also a problem for GPars as well as GroovyFX. Both projects must
> therefore stay with 1.11 until this is fixed.
> Workaround is explained on the original thread: http://forums.gradle.org/gradle/topics/groovyfx_build_fails_with_gradle_1_12_but_succeeds_with_1_11

Resounding success. Thanks Luke.


PS Your email replies (at least on this list) can be hard to read since
there is no distinction between what you are replying to and your
reply :-(

--
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[hidden email]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [hidden email]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Regression list for 1.12

Luke Daley-2
 



On 8 May 2014 at 6:52:09 pm, Russel Winder ([hidden email](mailto:[hidden email])) wrote:

> On Thu, 2014-05-08 at 17:36 +1000, Luke Daley wrote:  
> >  
> > On 8 May 2014 at 5:03:00 pm(http://airmail.calendar/2014-05-08%2017:03:00%20AEST), Russel Winder ([hidden email](mailto:[hidden email])) wrote:  
> >  
> > On Thu, 2014-05-08 at 11:21 +1000(http://airmail.calendar/2014-05-08%2011:21:00%20AEST), Adam Murdoch wrote:  
> > […]  
> > > > 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?  
> >  
> > This is also a problem for GPars as well as GroovyFX. Both projects must  
> > therefore stay with 1.11 until this is fixed.  
> > Workaround is explained on the original thread: http://forums.gradle.org/gradle/topics/groovyfx_build_fails_with_gradle_1_12_but_succeeds_with_1_11 
>  
> Resounding success. Thanks Luke.  
>  
>  
> PS Your email replies (at least on this list) can be hard to read since  
> there is no distinction between what you are replying to and your  
> reply :-(  

Thanks for pointing this out. I didn’t realise my client was doing that.

—  

Luke Daley  
Gradleware
Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email