Re: Breaking changes in 3.0 [was: Re: 2.5.0-rc-3]

2018-05-24 Thread Jesper Steen Møller
On 23 May 2018, at 13.24, Cédric Champeau wrote: > > +1, regarding indy by default, I wonder if we could provide the "old" MOP as > a backward compatibility runtime jar... > Yes, but that would be pretty tricky if we want to target JPMS too, due to split packages.

Re: Breaking changes in 3.0 [was: Re: 2.5.0-rc-3]

2018-05-23 Thread Daniel.Sun
> I wonder if we could provide the "old" MOP as a backward compatibility runtime jar... +1 P.S. when indy is enabled by default, Groovy's performance goes worse... -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Breaking changes in 3.0 [was: Re: 2.5.0-rc-3]

2018-05-23 Thread Cédric Champeau
+1, regarding indy by default, I wonder if we could provide the "old" MOP as a backward compatibility runtime jar... Le mer. 23 mai 2018 à 13:11, Jesper Steen Møller a écrit : > > > On 23 May 2018, at 12.23, Russel Winder wrote: > > > > On Wed,

Breaking changes in 3.0 [was: Re: 2.5.0-rc-3]

2018-05-23 Thread Jesper Steen Møller
> On 23 May 2018, at 12.23, Russel Winder wrote: > > On Wed, 2018-05-23 at 00:28 +1000, Paul King wrote: >> No plans to go to 18/19 model at this stage. >> >> If we push for an early 3.0, some of the breaking changes will have to be >> deferred. >> A very quick release

Re: 2.5.0-rc-3

2018-05-23 Thread Russel Winder
On Wed, 2018-05-23 at 00:28 +1000, Paul King wrote: > No plans to go to 18/19 model at this stage. > > If we push for an early 3.0, some of the breaking changes will have to be > deferred. > A very quick release after 3.0 could easily be a 3.1 if it was needed. > > The next major release (4.0)

Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-3 released

2018-05-23 Thread Daniel.Sun
Here is the jitpack link: https://jitpack.io/#apache/groovy/GROOVY_2_5_X-SNAPSHOT and here is the sample project to show how to use jitpack: https://github.com/danielsun1106/try-jitpack Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-3 released

2018-05-22 Thread Daniel.Sun
GROOVY-8595 is fixed in 2.5.0 GA. Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Groovy 2.5.0-rc-3 fails to break Gant [was Groovy 2.5.0-rc-2 breaks Gant]

2018-05-22 Thread Remko Popma
Glad to hear that. Remko On Wed, May 23, 2018 at 1:55 Russel Winder <rus...@winder.org.uk> wrote: > Hi, > > All Gant master/HEAD tests pass with Groovy 2.5.0-rc-3. > > :-) > > -- > Russel. > == > Dr Russel Winder

Re: 2.5.0-rc-3

2018-05-22 Thread mg
etreff: Re: 2.5.0-rc-3 No plans to go to 18/19 model at this stage. If we push for an early 3.0, some of the breaking changes will have to be deferred.A very quick release after 3.0 could easily be a 3.1 if it was needed. The next major release (4.0) would be when we had tackled (a signifi

Re: [ANNOUNCE] Apache Groovy 2.5.0-rc-3 released

2018-05-22 Thread Daniel.Sun
Nice. Thank you, Paul. Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Groovy 2.5.0-rc-3 fails to break Gant [was Groovy 2.5.0-rc-2 breaks Gant]

2018-05-22 Thread Russel Winder
Hi, All Gant master/HEAD tests pass with Groovy 2.5.0-rc-3. :-) -- Russel. == Dr Russel Winder t: +44 20 7585 2200 41 Buckmaster Roadm: +44 7770 465 077 London SW11 1EN, UK w: www.russel.org.uk signature.asc Description: This is a digitally

[ANNOUNCE] Apache Groovy 2.5.0-rc-3 released

2018-05-22 Thread Paul King
Dear community, The Apache Groovy team is pleased to announce version 2.5.0-rc-3 of Apache Groovy. Apache Groovy is a multi-facet programming language for the JVM. Further details can be found at the http://groovy.apache.org website. Pending any last minute feedback we anticipate this being

Re: 2.5.0-rc-3

2018-05-22 Thread Russel Winder
On Tue, 2018-05-22 at 15:06 +0200, mg wrote: > Is the intention to switch to a rapid major release cycle like Windows, > Java, etc ? If yes: Shouldn't we then call the next major release Groovy 18 > (or 19, depending on year of release) ? > Could also be: groovy 2.6 -> groovy 18.0groovy 3.0 ->

[RESULT][VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-22 Thread Paul King
The vote has passed with 4 binding +1 votes and 4 additional +1 votes. I'll proceed with next steps. Cheers, Paul. On Sun, May 20, 2018 at 1:40 AM, Paul King <pa...@asert.com.au> wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy

Re: 2.5.0-rc-3

2018-05-22 Thread Paul King
rage/etc)... (?) > > > Ursprüngliche Nachricht > Von: Cédric Champeau <cedric.champ...@gmail.com> > Datum: 22.05.18 13:31 (GMT+01:00) > An: dev@groovy.apache.org > Cc: Paul King <pa...@asert.com.au> > Betreff: Re: 2.5.0-rc-3 > > Yeah.

Re: 2.5.0-rc-3

2018-05-22 Thread mg
00) An: dev@groovy.apache.org Cc: Paul King <pa...@asert.com.au> Betreff: Re: 2.5.0-rc-3 Yeah. Doesn't prevent us from having a quick 4.0 with module revamp if we're extremely good :) Le mar. 22 mai 2018 à 13:29, Jesper Steen Møller <jes...@selskabet.org> a écrit  : And postpone module revamp?

Re: 2.5.0-rc-3

2018-05-22 Thread Cédric Champeau
Yeah. Doesn't prevent us from having a quick 4.0 with module revamp if we're extremely good :) Le mar. 22 mai 2018 à 13:29, Jesper Steen Møller a écrit : > And postpone module revamp? > > -Jesper > > On 22 May 2018, at 13.27, Cédric Champeau >

Re: 2.5.0-rc-3

2018-05-22 Thread Jesper Steen Møller
And postpone module revamp? -Jesper > On 22 May 2018, at 13.27, Cédric Champeau wrote: > > I think we should slim down what Groovy 3 is, make it Parrot + JDK 8 > basically. > > Le mar. 22 mai 2018 à 13:22, Paul King

Re: 2.5.0-rc-3

2018-05-22 Thread Cédric Champeau
I think we should slim down what Groovy 3 is, make it Parrot + JDK 8 basically. Le mar. 22 mai 2018 à 13:22, Paul King a écrit : > The question is really (most of) Parrot on JDK7+ or Parrot on JDK8+ sooner. > > > On Tue, May 22, 2018 at 7:55 PM, Daniel.Sun

Re: 2.5.0-rc-3

2018-05-22 Thread Paul King
The question is really (most of) Parrot on JDK7+ or Parrot on JDK8+ sooner. On Tue, May 22, 2018 at 7:55 PM, Daniel.Sun wrote: > As a user, if you ask me whether I need the Parrot or not, my answer will > always be yes even if I seldom use it ;-) > > Cheers, > Daniel.Sun > >

Re: 2.5.0-rc-3

2018-05-22 Thread Daniel.Sun
As a user, if you ask me whether I need the Parrot or not, my answer will always be yes even if I seldom use it ;-) Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: 2.5.0-rc-3

2018-05-22 Thread Paul King
On Mon, May 21, 2018 at 2:49 AM, Daniel.Sun wrote: > I am going to release 2.6.0-alpha-4 after 2.5.0 GA is released. Maybe do another alpha for 3.0 next since I will do a poll on the users list to see if anyone still needs Parrot on JDK7. Cheers, Paul. > Cheers, >

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-22 Thread Paul King
a...@asert.com.au> > Date: Tue, May 22, 2018 at 12:22 PM > Subject: Re: [VOTE] Release Apache Groovy 2.5.0-rc-3 > To: Remko Popma <remko.po...@gmail.com> > > > The warnings are by design. The java.time classes are only in JDK8, so our > extensions wouldn't make sense

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-22 Thread Remko Popma
:22 PM > Subject: Re: [VOTE] Release Apache Groovy 2.5.0-rc-3 > To: Remko Popma <remko.po...@gmail.com> > > > The warnings are by design. The java.time classes are only in JDK8, so our > extensions wouldn't make sense to load in JDK7. > > The windows warning is I

Fwd: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-21 Thread Paul King
Sorry, I accidentally went off-list. -- Forwarded message -- From: Paul King <pa...@asert.com.au> Date: Tue, May 22, 2018 at 12:22 PM Subject: Re: [VOTE] Release Apache Groovy 2.5.0-rc-3 To: Remko Popma <remko.po...@gmail.com> The warnings are by design. The java.

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-21 Thread Remko Popma
If >> there is interest I would like to generate auto-completion scripts for all >> tools, if they are all picocli-based that becomes easier. >> >> groovy.util.CliBuilder now has two deprecated setParser methods. I >> believe the intention is that the one on line 60 sh

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-21 Thread Paul King
0 should be named getParser instead? > Also, should a deprecated getter/setter for Options be added? > > The docs for the grape command line tool (groovy-2.5.0-rc-3/html/ > documentation/grape.html#Grape-CommandLineTool) is a bit out of date: > missing the uninstall subcommand and missing the

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-21 Thread Paul King
No bug in your example. X is picked up correctly normally but not for the forward reference in Daniel's example. So in Daniel's example the forward reference issue is one bug (now fixed). As to whether there is another bug I haven't checked. I'd say quite possibly. On Mon, May 21, 2018 at 8:32

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Paul King
It's a requirement to keep the vote open to account for subsequent -1 votes (except in circumstances like an emergency security fix). On Mon, May 21, 2018 at 2:59 PM, Remko Popma wrote: > > > > On May 21, 2018, at 13:35, Daniel.Sun wrote: > > > > My

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Remko Popma
> On May 21, 2018, at 13:35, Daniel.Sun wrote: > > My pleasure :-) > > P.S. You've collected more than three +1 from PMC members. Still probably good to keep the vote open for the announced 72 hours in case someone finds a showstopper. Remko > > Cheers, > Daniel.Sun >

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Daniel.Sun
My pleasure :-) P.S. You've collected more than three +1 from PMC members. Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Paul King
I suspect there is some stray "X" class on the test classpath which keeps the early checks happy until later resolution. Thanks for the fix. Cheers, Paul. On Mon, May 21, 2018 at 1:29 AM, Daniel.Sun wrote: > +1 > > All tests pass on my machine. Here is my machine info: > ```

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Jochen Theodorou
+1 On 19.05.2018 17:40, Paul King wrote: Dear development community, I am happy to start the VOTE thread for a Groovy 2.5.0-rc-3 release! This release includes 27 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123

Re: 2.5.0-rc-3

2018-05-20 Thread Daniel.Sun
I am going to release 2.6.0-alpha-4 after 2.5.0 GA is released. Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Guillaume Laforge
+1 Le dim. 20 mai 2018 à 18:30, Daniel.Sun a écrit : > "GROOVY-6167" should be finally fixed by > 1) fix resolving [1] (pushed just now, will be included in 2.5.0 GA) > 2) fix type inference [2] > > But it's really weird, I still don't know the reason why the test[3] always >

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Daniel.Sun
"GROOVY-6167" should be finally fixed by 1) fix resolving [1] (pushed just now, will be included in 2.5.0 GA) 2) fix type inference [2] But it's really weird, I still don't know the reason why the test[3] always passes... P.S. The issue number should be 6167(not 6171), it is fixed by too

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Daniel.Sun
+1 All tests pass on my machine. Here is my machine info: ``` Gradle 4.7 Build time: 2018-04-18 09:09:12 UTC Revision: b9a962bf70638332300e7f810689cb2febbd4a6c Groovy:

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Andres Almiray
+1 Sent from my primitive Tricorder > On 20 May 2018, at 18:45, Russel Winder <rus...@winder.org.uk> wrote: > > >> [ ] +1 Release Apache Groovy 2.5.0-rc-3 >> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >> [ ] -1 Do not release

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-20 Thread Russel Winder
> [ ] +1 Release Apache Groovy 2.5.0-rc-3 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.5.0-rc-3 because... > > +1 -- Russel. == Dr Russel Winder t: +44 20 7585 220

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-19 Thread John Wagenleitner
+1 (binding) On Sat, May 19, 2018 at 8:40 AM Paul King <pa...@asert.com.au> wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.0-rc-3 release! > > This release includes 27 bug fixes/improvements as outlined in th

[VOTE] Release Apache Groovy 2.5.0-rc-3

2018-05-19 Thread Paul King
Dear development community, I am happy to start the VOTE thread for a Groovy 2.5.0-rc-3 release! This release includes 27 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12343166 Tag: https://git1-us-west.apache.org

Re: 2.5.0-rc-3

2018-05-18 Thread Remko Popma
Thanks Daniel! > On May 18, 2018, at 22:00, Daniel.Sun wrote: > > FYI > https://github.com/groovy/groovy-website/blob/master/site/src/site/releasenotes/groovy-2.5.adoc > > http://groovy-lang.org/releasenotes/groovy-2.5.html > > Cheers, > Daniel.Sun > > > > > > > -- >

Re: 2.5.0-rc-3

2018-05-18 Thread Daniel.Sun
FYI https://github.com/groovy/groovy-website/blob/master/site/src/site/releasenotes/groovy-2.5.adoc http://groovy-lang.org/releasenotes/groovy-2.5.html Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: 2.5.0-rc-3

2018-05-18 Thread Daniel.Sun
Try the jitpack https://github.com/danielsun1106/try-jitpack Or clone apache/groovy project and run `./gradlew installGroovy` to build from source and get the snapshot Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: 2.5.0-rc-3

2018-05-18 Thread Remko Popma
Where do the release notes live? I can’t find them on GitHub. Remko > On May 18, 2018, at 20:20, Paul King wrote: > > > Last call for changes in rc-3. I hope to prepare the candidate for voting > tomorrow. > > If all goes well, please then consider the 2_5_X branch