Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[J. David Beutel]

Option 2 or 3.  I'm running Grails 2.5.3 on JDK 8, although I intend to 
upgrade to the current versions, when I have the time for that.



On 2018-06-13 07:53 , Scott Hickey wrote:
I've have always appreciated the willingness of the Groovy team to 
recognize that enterprises can't always move quickly to current 
versions of Java.


At Mutual of Omaha, we do have almost everything running on JDK 8 now. 
We are actively trying to get our few remaining Grails 2.x versions 
upgraded to a current version of Grails.


I don't think that focusing only on Groovy 3 at this point would 
adversely affect our company.



On Wed, Jun 13, 2018 at 2:06 AM Paul King > wrote:



Hi everyone,

There was some discussion at gr8conf about how to speed up
delivery of Groovy 3.0. Some of that discussion was around the
scope of what we want to include and have yet to complete in 3.0
but I won't discuss that right now.

One of the other discussion points was Groovy around 2.6. As many
of you know, we have released alpha versions of Groovy 2.6. That
version is a backport of most but not all of Groovy 3.0 to JDK7
including the Parrot parser (though it isn't enabled by default).
The purpose of this version has always been to assist
people/projects wanting to use the Parrot parser but who might be
stuck on JDK7. So in some sense it is an intermediate version to
assist with porting towards Groovy 3.0. While that is still a
noble goal in theory, in practice, many of our users are already
on JDK8 and we have limited resources to work on many potential areas.

With that in mind, we'd like to understand the preferences in our
user base for the following two options:

Option 1: please continue releasing the best possible 2.6 even if
that slows down the final release of Groovy 3.0 and delays further
work on better support for JDK9+.

Option 2: please release one more alpha of 2.6 over the next month
or so which will become the best version to use to assist porting
for users stuck on JDK7 and then focus on 3.0. The 2.6 branch will
essentially be retired though we will consider PRs from the
community for critical fixes.

Feedback welcome.

Cheers, Paul.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Paul King]

On Wed, Jun 13, 2018 at 5:11 PM, David Dawson <
david.daw...@simplicityitself.com> wrote:

> I would vote 2.
>
> Actually, i would vote 3) abandon 2.6 immediately.
>

We identified a few major things that were broken in the previous alpha
release of
2.6 but only due to trivial packaging issues, hence the plan to do one more
release.

Also, Jesper identified a few things that can easily be aligned from 3.0 in
a very short period of time. I am happy to wait for his thumbs up before
proceeding.

I am also keen on releasing another alpha of 3.0 at the same time as the
2.6 alpha.
I believe that will make our life easier when answering future
support-oriented questions
about 2.6 on the mailing list going forward.

So, doing one more alpha release of 2.6 has minimal impact on 3.0 timing
and leaves
us in as clean a state as can be hoped for when retiring a previously
planned branch.

Cheers, Paul.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Paul King]

On Wed, Jun 13, 2018 at 10:11 PM, Corum, Michael  wrote:

> If 3.0 will still support JDK8, I’d vote for option 3 as well.  If 3 will
> require 9, then maybe option 2.
>
>
>
Groovy 3.0 has JDK8 as minimum.

Cheers, Paul.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[h2gr]

Bloated, is the word I was looking for...

Den 2018-06-13 19:46, skrev h...@abula.org:

I did come from Java myself, and I understand the argument to ease the
transition from Java to Groovy, but as Java adopts language features
from Groovy, I worry that supporting both syntaxes will create a more
complex language with more options, more stuff to learn, and less
clarity.

Besides, in my experience developers are quite able to handle
different languages. Granted, Groovy should be easy to read and
understand for developers coming from Java (and other) languages, but
not every language feature in other languages need to be valid Groovy
code as well.

H2


Den 2018-06-13 17:24, skrev MG:

On 6/13/2018 10:24 AM, h...@abula.org wrote:
(I may be alone on this one, but I'd even suggest to consider some of 
the Java syntax compatibility, if this helps speed up Groovy 3. If I 
need to write Java code, I can always put it in .java files.)


Java-syntax-compatibility-only-support in Groovy is not there to be
used by Groovy developers (see previous discussions about warning when
using these constructs), but to support copy & paste compatibility for
people considering switching from Java.
I understand where you are coming from, but imho the closesness to
Java always has been another strong argument for Groovy, and
considering supporting Java syntax constructs in Groovy 3.0 through
the Parrot parser seems pretty straightforward I think we should keep
doing this.

An alternative would be to support a tool which auto-converts from
Java to Groovy (I would estimate this would be more effort, and it
does not really give the "copy & paste Java code and it is Groovy"
experience). Or IntelliJ/Eclipse/Netbeans could support this as part
of their respective code refactoring support...

Cheers,
mg




Den 2018-06-13 10:08, skrev Mario Garcia:

I would say 3 as well

2018-06-13 10:04 GMT+02:00 Robert Oschwald 
:



Same with me. Option 3 seems best, even when some of our projects
are still on Grails 2.

Am 13.06.2018 um 09:50 schrieb Søren Berg Glasius
:
While the project I'm on is still on JDK 7, but due to Grails 2.x I
think that option 3 is the best way to move forward (and nudge
projects on to a higher version of Grails as well).

/Søren

On Wed, 13 Jun 2018, 09.42 , 
wrote:

I agree on option 3 (abandon 2.6 immediately).

JDK 6 or 7 is not in use anywhere that I have project visibility.

Full support for JKD9+ is becoming a pressing issue. Users are
concerned about the ability of Groovy to run on future JDK releases
(including GraalVM), more than legacy support.

Best Regards

FROM: Paolo Di Tommaso [mailto:paolo.ditomm...@gmail.com]
SENT: Wednesday, June 13, 2018 3:18 AM
TO: users@groovy.apache.org
SUBJECT: Re: [DISCUSS] Groovy 2.6 potential retirement to focus on
Groovy 3.0

I agree on option 3 (abandon 2.6 immediately).

Full support for JKD9+ is becoming a pressing issue. Users are
concerned about the ability of Groovy to run on future JDK releases
(including GraalVM), more than legacy support.

Cheers,

p

On Wed, Jun 13, 2018 at 9:11 AM, David Dawson
 wrote:

I would vote 2.

Actually, i would vote 3) abandon 2.6 immediately.

No projects I have any knowledge of still use jdk 7.

FROM: pa...@asert.com.au

SENT: 13 June 2018 08:06

TO: users@groovy.apache.org

REPLY TO: users@groovy.apache.org

SUBJECT: [DISCUSS] Groovy 2.6 potential retirement to focus on
Groovy 3.0

Hi everyone,

There was some discussion at gr8conf about how to speed up delivery
of Groovy 3.0. Some of that discussion was around the scope of what
we want to include and have yet to complete in 3.0 but I won't
discuss that right now.

One of the other discussion points was Groovy around 2.6. As many 
of

you know, we have released alpha versions of Groovy 2.6. That
version is a backport of most but not all of Groovy 3.0 to JDK7
including the Parrot parser (though it isn't enabled by default).
The purpose of this version has always been to assist
people/projects wanting to use the Parrot parser but who might be
stuck on JDK7. So in some sense it is an intermediate version to
assist with porting towards Groovy 3.0. While that is still a noble
goal in theory, in practice, many of our users are already on JDK8
and we have limited resources to work on many potential areas.

With that in mind, we'd like to understand the preferences in our
user base for the following two options:

Option 1: please continue releasing the best possible 2.6 even if
that slows down the final release of Groovy 3.0 and delays further
work on better support for JDK9+.

Option 2: please release one more alpha of 2.6 over the next month
or so which will become the best version to use to assist porting
for users stuck on JDK7 and then focus on 3.0. The 2.6 branch will
essentially be retired though we will consider PRs from the
community for critical fixes.

Feedback welcome.

Cheers, Paul.

-- Best regards / Med venlig hilsen,

Søren Berg Glasius

Hedevej 1, Gl. Rye, 8680 Ry, Denmark

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Scott Hickey]

I've have always appreciated the willingness of the Groovy team to
recognize that enterprises can't always move quickly to current versions of
Java.

At Mutual of Omaha, we do have almost everything running on JDK 8 now. We
are actively trying to get our few remaining Grails 2.x versions upgraded
to a current version of Grails.

I don't think that focusing only on Groovy 3 at this point would adversely
affect our company.


On Wed, Jun 13, 2018 at 2:06 AM Paul King  wrote:

>
> Hi everyone,
>
> There was some discussion at gr8conf about how to speed up delivery of
> Groovy 3.0. Some of that discussion was around the scope of what we want to
> include and have yet to complete in 3.0 but I won't discuss that right now.
>
> One of the other discussion points was Groovy around 2.6. As many of you
> know, we have released alpha versions of Groovy 2.6. That version is a
> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
> parser (though it isn't enabled by default). The purpose of this version
> has always been to assist people/projects wanting to use the Parrot parser
> but who might be stuck on JDK7. So in some sense it is an intermediate
> version to assist with porting towards Groovy 3.0. While that is still a
> noble goal in theory, in practice, many of our users are already on JDK8
> and we have limited resources to work on many potential areas.
>
> With that in mind, we'd like to understand the preferences in our user
> base for the following two options:
>
> Option 1: please continue releasing the best possible 2.6 even if that
> slows down the final release of Groovy 3.0 and delays further work on
> better support for JDK9+.
>
> Option 2: please release one more alpha of 2.6 over the next month or so
> which will become the best version to use to assist porting for users stuck
> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
> though we will consider PRs from the community for critical fixes.
>
> Feedback welcome.
>
> Cheers, Paul.
>
>
>

GraalVM/Truffle ?

[MG]

Since GraalVM (https://en.wikipedia.org/wiki/GraalVM) was mentioned here 
recently: Do we have any statement on plans of Groovy with regards to 
GraalVM, including Truffle ? It might be good to have an official 
statement here on the main Groovy page and on Wikipedia 
(https://en.wikipedia.org/wiki/Apache_Groovy), even if it e.g., in 
essence, just states "Groovy runs/will run fine on GraalVM", "The 
Truffle license (GPL 2.0 w CP exception) is not compatible with Apache 
Groovy" or "Truffle makes no sense for Groovy (at this point)"...


Cheers,
mg

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[MG]

On 6/13/2018 10:24 AM, h...@abula.org wrote:
(I may be alone on this one, but I'd even suggest to consider some of 
the Java syntax compatibility, if this helps speed up Groovy 3. If I 
need to write Java code, I can always put it in .java files.)


Java-syntax-compatibility-only-support in Groovy is not there to be used 
by Groovy developers (see previous discussions about warning when using 
these constructs), but to support copy & paste compatibility for people 
considering switching from Java.
I understand where you are coming from, but imho the closesness to Java 
always has been another strong argument for Groovy, and considering 
supporting Java syntax constructs in Groovy 3.0 through the Parrot 
parser seems pretty straightforward I think we should keep doing this.


An alternative would be to support a tool which auto-converts from Java 
to Groovy (I would estimate this would be more effort, and it does not 
really give the "copy & paste Java code and it is Groovy" experience). 
Or IntelliJ/Eclipse/Netbeans could support this as part of their 
respective code refactoring support...


Cheers,
mg




Den 2018-06-13 10:08, skrev Mario Garcia:

I would say 3 as well

2018-06-13 10:04 GMT+02:00 Robert Oschwald :


Same with me. Option 3 seems best, even when some of our projects
are still on Grails 2.

Am 13.06.2018 um 09:50 schrieb Søren Berg Glasius
:
While the project I'm on is still on JDK 7, but due to Grails 2.x I
think that option 3 is the best way to move forward (and nudge
projects on to a higher version of Grails as well).

/Søren

On Wed, 13 Jun 2018, 09.42 , 
wrote:

I agree on option 3 (abandon 2.6 immediately).

JDK 6 or 7 is not in use anywhere that I have project visibility.

Full support for JKD9+ is becoming a pressing issue. Users are
concerned about the ability of Groovy to run on future JDK releases
(including GraalVM), more than legacy support.

Best Regards

FROM: Paolo Di Tommaso [mailto:paolo.ditomm...@gmail.com]
SENT: Wednesday, June 13, 2018 3:18 AM
TO: users@groovy.apache.org
SUBJECT: Re: [DISCUSS] Groovy 2.6 potential retirement to focus on
Groovy 3.0

I agree on option 3 (abandon 2.6 immediately).

Full support for JKD9+ is becoming a pressing issue. Users are
concerned about the ability of Groovy to run on future JDK releases
(including GraalVM), more than legacy support.

Cheers,

p

On Wed, Jun 13, 2018 at 9:11 AM, David Dawson
 wrote:

I would vote 2.

Actually, i would vote 3) abandon 2.6 immediately.

No projects I have any knowledge of still use jdk 7.

FROM: pa...@asert.com.au

SENT: 13 June 2018 08:06

TO: users@groovy.apache.org

REPLY TO: users@groovy.apache.org

SUBJECT: [DISCUSS] Groovy 2.6 potential retirement to focus on
Groovy 3.0

Hi everyone,

There was some discussion at gr8conf about how to speed up delivery
of Groovy 3.0. Some of that discussion was around the scope of what
we want to include and have yet to complete in 3.0 but I won't
discuss that right now.

One of the other discussion points was Groovy around 2.6. As many of
you know, we have released alpha versions of Groovy 2.6. That
version is a backport of most but not all of Groovy 3.0 to JDK7
including the Parrot parser (though it isn't enabled by default).
The purpose of this version has always been to assist
people/projects wanting to use the Parrot parser but who might be
stuck on JDK7. So in some sense it is an intermediate version to
assist with porting towards Groovy 3.0. While that is still a noble
goal in theory, in practice, many of our users are already on JDK8
and we have limited resources to work on many potential areas.

With that in mind, we'd like to understand the preferences in our
user base for the following two options:

Option 1: please continue releasing the best possible 2.6 even if
that slows down the final release of Groovy 3.0 and delays further
work on better support for JDK9+.

Option 2: please release one more alpha of 2.6 over the next month
or so which will become the best version to use to assist porting
for users stuck on JDK7 and then focus on 3.0. The 2.6 branch will
essentially be retired though we will consider PRs from the
community for critical fixes.

Feedback welcome.

Cheers, Paul.

--

Best regards / Med venlig hilsen,

Søren Berg Glasius

Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[MG]

Option 2 or 3 from my side.
I have thought about this, and given the fast movement of the Java 
universe at the moment it seems the right move, from a resources and 
public perception point of view.


Also, Groovy 2.5 is not too shabby, so still being on JDK 7 it is not 
like "no Groovy for you" ;-)


Cheers,
mg


On 6/13/2018 9:05 AM, Paul King wrote:


Hi everyone,

There was some discussion at gr8conf about how to speed up delivery of 
Groovy 3.0. Some of that discussion was around the scope of what we 
want to include and have yet to complete in 3.0 but I won't discuss 
that right now.


One of the other discussion points was Groovy around 2.6. As many of 
you know, we have released alpha versions of Groovy 2.6. That version 
is a backport of most but not all of Groovy 3.0 to JDK7 including the 
Parrot parser (though it isn't enabled by default). The purpose of 
this version has always been to assist people/projects wanting to use 
the Parrot parser but who might be stuck on JDK7. So in some sense it 
is an intermediate version to assist with porting towards Groovy 3.0. 
While that is still a noble goal in theory, in practice, many of our 
users are already on JDK8 and we have limited resources to work on 
many potential areas.


With that in mind, we'd like to understand the preferences in our user 
base for the following two options:


Option 1: please continue releasing the best possible 2.6 even if that 
slows down the final release of Groovy 3.0 and delays further work on 
better support for JDK9+.


Option 2: please release one more alpha of 2.6 over the next month or 
so which will become the best version to use to assist porting for 
users stuck on JDK7 and then focus on 3.0. The 2.6 branch will 
essentially be retired though we will consider PRs from the community 
for critical fixes.


Feedback welcome.

Cheers, Paul.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Eric Helgeson]

Agree with option 3 as well. If you're stuck on pre jdk8 and have groovy
2.5 - that's a pretty good situation. JDK9/10/11+ compatibility is the
direction the language needs to go.

On Wed, Jun 13, 2018 at 8:19 AM sigzero  wrote:

> Option 3.
>
> You can always revisit the 2.6 branch if that becomes necessary. Resources
> being scarce (as others have said), put them where they are needed on
> Groovy 3.
>
> --
> Bob
>
> On Wed, Jun 13, 2018 at 8:11 AM, Corum, Michael  wrote:
>
>> If 3.0 will still support JDK8, I’d vote for option 3 as well.  If 3 will
>> require 9, then maybe option 2.
>>
>>
>>
>> *Michael Corum*
>>
>> VP, Technical Architecture Solutions
>>
>>
>>
>> *RGA Reinsurance Company*
>>
>> *16600 Swingley Ridge Road
>> *
>>
>> *Chesterfield, Missouri
>> 
>> 6301701706*
>>
>> *T* 636.736.7066
>>
>> *www.rgare.com *
>>
>>
>>
>> *From: *Paul King 
>> *Reply-To: *"users@groovy.apache.org" , "
>> pa...@asert.com.au" 
>> *Date: *Wednesday, June 13, 2018 at 2:06 AM
>> *To: *"users@groovy.apache.org" 
>> *Subject: *[DISCUSS] Groovy 2.6 potential retirement to focus on Groovy
>> 3.0
>>
>>
>>
>> External e-mail. Use caution! / Courriel externe. Faites attention!
>> --
>>
>>
>>
>> Hi everyone,
>>
>>
>>
>> There was some discussion at gr8conf about how to speed up delivery of
>> Groovy 3.0. Some of that discussion was around the scope of what we want to
>> include and have yet to complete in 3.0 but I won't discuss that right now.
>>
>>
>>
>> One of the other discussion points was Groovy around 2.6. As many of you
>> know, we have released alpha versions of Groovy 2.6. That version is a
>> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
>> parser (though it isn't enabled by default). The purpose of this version
>> has always been to assist people/projects wanting to use the Parrot parser
>> but who might be stuck on JDK7. So in some sense it is an intermediate
>> version to assist with porting towards Groovy 3.0. While that is still a
>> noble goal in theory, in practice, many of our users are already on JDK8
>> and we have limited resources to work on many potential areas.
>>
>>
>>
>> With that in mind, we'd like to understand the preferences in our user
>> base for the following two options:
>>
>>
>>
>> Option 1: please continue releasing the best possible 2.6 even if that
>> slows down the final release of Groovy 3.0 and delays further work on
>> better support for JDK9+.
>>
>>
>>
>> Option 2: please release one more alpha of 2.6 over the next month or so
>> which will become the best version to use to assist porting for users stuck
>> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
>> though we will consider PRs from the community for critical fixes.
>>
>>
>>
>> Feedback welcome.
>>
>>
>>
>> Cheers, Paul.
>>
>>
>>
>>
>>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[sigzero]

Option 3.

You can always revisit the 2.6 branch if that becomes necessary. Resources
being scarce (as others have said), put them where they are needed on
Groovy 3.

--
Bob

On Wed, Jun 13, 2018 at 8:11 AM, Corum, Michael  wrote:

> If 3.0 will still support JDK8, I’d vote for option 3 as well.  If 3 will
> require 9, then maybe option 2.
>
>
>
> *Michael Corum*
>
> VP, Technical Architecture Solutions
>
>
>
> *RGA Reinsurance Company*
>
> *16600 Swingley Ridge Road
> *
>
> *Chesterfield, Missouri
> 
> 6301701706*
>
> *T* 636.736.7066
>
> *www.rgare.com *
>
>
>
> *From: *Paul King 
> *Reply-To: *"users@groovy.apache.org" , "
> pa...@asert.com.au" 
> *Date: *Wednesday, June 13, 2018 at 2:06 AM
> *To: *"users@groovy.apache.org" 
> *Subject: *[DISCUSS] Groovy 2.6 potential retirement to focus on Groovy
> 3.0
>
>
>
> External e-mail. Use caution! / Courriel externe. Faites attention!
> --
>
>
>
> Hi everyone,
>
>
>
> There was some discussion at gr8conf about how to speed up delivery of
> Groovy 3.0. Some of that discussion was around the scope of what we want to
> include and have yet to complete in 3.0 but I won't discuss that right now.
>
>
>
> One of the other discussion points was Groovy around 2.6. As many of you
> know, we have released alpha versions of Groovy 2.6. That version is a
> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
> parser (though it isn't enabled by default). The purpose of this version
> has always been to assist people/projects wanting to use the Parrot parser
> but who might be stuck on JDK7. So in some sense it is an intermediate
> version to assist with porting towards Groovy 3.0. While that is still a
> noble goal in theory, in practice, many of our users are already on JDK8
> and we have limited resources to work on many potential areas.
>
>
>
> With that in mind, we'd like to understand the preferences in our user
> base for the following two options:
>
>
>
> Option 1: please continue releasing the best possible 2.6 even if that
> slows down the final release of Groovy 3.0 and delays further work on
> better support for JDK9+.
>
>
>
> Option 2: please release one more alpha of 2.6 over the next month or so
> which will become the best version to use to assist porting for users stuck
> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
> though we will consider PRs from the community for critical fixes.
>
>
>
> Feedback welcome.
>
>
>
> Cheers, Paul.
>
>
>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Corum, Michael]

If 3.0 will still support JDK8, I’d vote for option 3 as well.  If 3 will 
require 9, then maybe option 2.

Michael Corum
VP, Technical Architecture Solutions

RGA Reinsurance Company
16600 Swingley Ridge Road
Chesterfield, Missouri 6301701706
T 636.736.7066
www.rgare.com

From: Paul King 
Reply-To: "users@groovy.apache.org" , 
"pa...@asert.com.au" 
Date: Wednesday, June 13, 2018 at 2:06 AM
To: "users@groovy.apache.org" 
Subject: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

External e-mail. Use caution! / Courriel externe. Faites attention!


Hi everyone,

There was some discussion at gr8conf about how to speed up delivery of Groovy 
3.0. Some of that discussion was around the scope of what we want to include 
and have yet to complete in 3.0 but I won't discuss that right now.

One of the other discussion points was Groovy around 2.6. As many of you know, 
we have released alpha versions of Groovy 2.6. That version is a backport of 
most but not all of Groovy 3.0 to JDK7 including the Parrot parser (though it 
isn't enabled by default). The purpose of this version has always been to 
assist people/projects wanting to use the Parrot parser but who might be stuck 
on JDK7. So in some sense it is an intermediate version to assist with porting 
towards Groovy 3.0. While that is still a noble goal in theory, in practice, 
many of our users are already on JDK8 and we have limited resources to work on 
many potential areas.

With that in mind, we'd like to understand the preferences in our user base for 
the following two options:

Option 1: please continue releasing the best possible 2.6 even if that slows 
down the final release of Groovy 3.0 and delays further work on better support 
for JDK9+.

Option 2: please release one more alpha of 2.6 over the next month or so which 
will become the best version to use to assist porting for users stuck on JDK7 
and then focus on 3.0. The 2.6 branch will essentially be retired though we 
will consider PRs from the community for critical fixes.

Feedback welcome.

Cheers, Paul.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Simon Sadedin]

As with everyone else: option 3, or even just solving the Java9+ issue
separate from 3.0 is much more important than JDK7.

Cheers,

Simon

On Wed, Jun 13, 2018 at 8:44 PM, Iván López  wrote:

> I also vote for Option 3. I think it is better to focus on JDK 9+ than in
> JDK 7.
>
> Regards, Iván.
>
> --
> @ilopmar 
>
> On 13 June 2018 at 11:30, Russel Winder  wrote:
>
>> On Wed, 2018-06-13 at 08:11 +0100, David Dawson wrote:
>> > I would vote 2.
>> >
>> > Actually, i would vote 3) abandon 2.6 immediately.
>> >
>>
>> I vote for Option 3, abandon 2.6 immediately.
>>
>> With so little resource, the Groovy project must focus on forward looking
>> work, not backward looking stuff. JDK10 is whee the current action is, and
>> where Groovy should be looking to be competitive.
>>
>> --
>> Russel.
>> ===
>> Dr Russel Winder  t: +44 20 7585 2200
>> 41 Buckmaster Road
>> 
>> m: +44 7770 465 077
>> London SW11 1EN, UK   w: www.russel.org.uk
>>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Iván López]

I also vote for Option 3. I think it is better to focus on JDK 9+ than in
JDK 7.

Regards, Iván.

--
@ilopmar 

On 13 June 2018 at 11:30, Russel Winder  wrote:

> On Wed, 2018-06-13 at 08:11 +0100, David Dawson wrote:
> > I would vote 2.
> >
> > Actually, i would vote 3) abandon 2.6 immediately.
> >
>
> I vote for Option 3, abandon 2.6 immediately.
>
> With so little resource, the Groovy project must focus on forward looking
> work, not backward looking stuff. JDK10 is whee the current action is, and
> where Groovy should be looking to be competitive.
>
> --
> 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
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Russel Winder]

On Wed, 2018-06-13 at 08:11 +0100, David Dawson wrote:
> I would vote 2.
> 
> Actually, i would vote 3) abandon 2.6 immediately.
> 

I vote for Option 3, abandon 2.6 immediately.

With so little resource, the Groovy project must focus on forward looking
work, not backward looking stuff. JDK10 is whee the current action is, and
where Groovy should be looking to be competitive.  

-- 
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 signed message part

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Christian Sperandio]

Hi,

For me, Groovy 3.0 is the most important thing.

Chris

Le mer. 13 juin 2018 à 09:06, Paul King  a écrit :

>
> Hi everyone,
>
> There was some discussion at gr8conf about how to speed up delivery of
> Groovy 3.0. Some of that discussion was around the scope of what we want to
> include and have yet to complete in 3.0 but I won't discuss that right now.
>
> One of the other discussion points was Groovy around 2.6. As many of you
> know, we have released alpha versions of Groovy 2.6. That version is a
> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
> parser (though it isn't enabled by default). The purpose of this version
> has always been to assist people/projects wanting to use the Parrot parser
> but who might be stuck on JDK7. So in some sense it is an intermediate
> version to assist with porting towards Groovy 3.0. While that is still a
> noble goal in theory, in practice, many of our users are already on JDK8
> and we have limited resources to work on many potential areas.
>
> With that in mind, we'd like to understand the preferences in our user
> base for the following two options:
>
> Option 1: please continue releasing the best possible 2.6 even if that
> slows down the final release of Groovy 3.0 and delays further work on
> better support for JDK9+.
>
> Option 2: please release one more alpha of 2.6 over the next month or so
> which will become the best version to use to assist porting for users stuck
> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
> though we will consider PRs from the community for critical fixes.
>
> Feedback welcome.
>
> Cheers, Paul.
>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[h2gr]

I say 3.

(I may be alone on this one, but I'd even suggest to consider some of 
the Java syntax compatibility, if this helps speed up Groovy 3. If I 
need to write Java code, I can always put it in .java files.)


Haakon Hansen



Den 2018-06-13 10:08, skrev Mario Garcia:

I would say 3 as well

2018-06-13 10:04 GMT+02:00 Robert Oschwald :


Same with me. Option 3 seems best, even when some of our projects
are still on Grails 2.

Am 13.06.2018 um 09:50 schrieb Søren Berg Glasius
:
While the project I'm on is still on JDK 7, but due to Grails 2.x I
think that option 3 is the best way to move forward (and nudge
projects on to a higher version of Grails as well).

/Søren

On Wed, 13 Jun 2018, 09.42 , 
wrote:

I agree on option 3 (abandon 2.6 immediately).

JDK 6 or 7 is not in use anywhere that I have project visibility.

Full support for JKD9+ is becoming a pressing issue. Users are
concerned about the ability of Groovy to run on future JDK releases
(including GraalVM), more than legacy support.

Best Regards

FROM: Paolo Di Tommaso [mailto:paolo.ditomm...@gmail.com]
SENT: Wednesday, June 13, 2018 3:18 AM
TO: users@groovy.apache.org
SUBJECT: Re: [DISCUSS] Groovy 2.6 potential retirement to focus on
Groovy 3.0

I agree on option 3 (abandon 2.6 immediately).

Full support for JKD9+ is becoming a pressing issue. Users are
concerned about the ability of Groovy to run on future JDK releases
(including GraalVM), more than legacy support.

Cheers,

p

On Wed, Jun 13, 2018 at 9:11 AM, David Dawson
 wrote:

I would vote 2.

Actually, i would vote 3) abandon 2.6 immediately.

No projects I have any knowledge of still use jdk 7.

FROM: pa...@asert.com.au

SENT: 13 June 2018 08:06

TO: users@groovy.apache.org

REPLY TO: users@groovy.apache.org

SUBJECT: [DISCUSS] Groovy 2.6 potential retirement to focus on
Groovy 3.0

Hi everyone,

There was some discussion at gr8conf about how to speed up delivery
of Groovy 3.0. Some of that discussion was around the scope of what
we want to include and have yet to complete in 3.0 but I won't
discuss that right now.

One of the other discussion points was Groovy around 2.6. As many of
you know, we have released alpha versions of Groovy 2.6. That
version is a backport of most but not all of Groovy 3.0 to JDK7
including the Parrot parser (though it isn't enabled by default).
The purpose of this version has always been to assist
people/projects wanting to use the Parrot parser but who might be
stuck on JDK7. So in some sense it is an intermediate version to
assist with porting towards Groovy 3.0. While that is still a noble
goal in theory, in practice, many of our users are already on JDK8
and we have limited resources to work on many potential areas.

With that in mind, we'd like to understand the preferences in our
user base for the following two options:

Option 1: please continue releasing the best possible 2.6 even if
that slows down the final release of Groovy 3.0 and delays further
work on better support for JDK9+.

Option 2: please release one more alpha of 2.6 over the next month
or so which will become the best version to use to assist porting
for users stuck on JDK7 and then focus on 3.0. The 2.6 branch will
essentially be retired though we will consider PRs from the
community for critical fixes.

Feedback welcome.

Cheers, Paul.

--

Best regards / Med venlig hilsen,

Søren Berg Glasius

Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Mario Garcia]

I would say 3 as well

2018-06-13 10:04 GMT+02:00 Robert Oschwald :

> Same with me. Option 3 seems best, even when some of our projects are
> still on Grails 2.
>
>
> Am 13.06.2018 um 09:50 schrieb Søren Berg Glasius :
>
> While the project I'm on is still on JDK 7, but due to Grails 2.x I think
> that option 3 is the best way to move forward (and nudge projects on to a
> higher version of Grails as well).
>
> /Søren
>
> On Wed, 13 Jun 2018, 09.42 ,  wrote:
>
>> I agree on option 3 (abandon 2.6 immediately).
>>
>>
>>
>> JDK 6 or 7 is not in use anywhere that I have project visibility.
>>
>>
>>
>> Full support for JKD9+ is becoming a pressing issue. Users are concerned
>> about the ability of Groovy to run on future JDK releases (including
>> GraalVM), more than legacy support.
>>
>>
>>
>> Best Regards
>>
>>
>>
>> *From:* Paolo Di Tommaso [mailto:paolo.ditomm...@gmail.com]
>> *Sent:* Wednesday, June 13, 2018 3:18 AM
>> *To:* users@groovy.apache.org
>> *Subject:* Re: [DISCUSS] Groovy 2.6 potential retirement to focus on
>> Groovy 3.0
>>
>>
>>
>> I agree on option 3 (abandon 2.6 immediately).
>>
>>
>>
>> Full support for JKD9+ is becoming a pressing issue. Users are concerned
>> about the ability of Groovy to run on future JDK releases (including
>> GraalVM), more than legacy support.
>>
>>
>>
>>
>>
>> Cheers,
>>
>> p
>>
>>
>>
>> On Wed, Jun 13, 2018 at 9:11 AM, David Dawson > simplicityitself.com> wrote:
>>
>> I would vote 2.
>>
>>
>>
>> Actually, i would vote 3) abandon 2.6 immediately.
>>
>>
>>
>> No projects I have any knowledge of still use jdk 7.
>>
>>
>>
>> *From:* pa...@asert.com.au
>>
>> *Sent:* 13 June 2018 08:06
>>
>> *To:* users@groovy.apache.org
>>
>> *Reply to:* users@groovy.apache.org
>>
>> *Subject:* [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy
>> 3.0
>>
>>
>>
>>
>>
>> Hi everyone,
>>
>>
>>
>> There was some discussion at gr8conf about how to speed up delivery of
>> Groovy 3.0. Some of that discussion was around the scope of what we want to
>> include and have yet to complete in 3.0 but I won't discuss that right now.
>>
>>
>>
>> One of the other discussion points was Groovy around 2.6. As many of you
>> know, we have released alpha versions of Groovy 2.6. That version is a
>> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
>> parser (though it isn't enabled by default). The purpose of this version
>> has always been to assist people/projects wanting to use the Parrot parser
>> but who might be stuck on JDK7. So in some sense it is an intermediate
>> version to assist with porting towards Groovy 3.0. While that is still a
>> noble goal in theory, in practice, many of our users are already on JDK8
>> and we have limited resources to work on many potential areas.
>>
>>
>>
>> With that in mind, we'd like to understand the preferences in our user
>> base for the following two options:
>>
>>
>>
>> Option 1: please continue releasing the best possible 2.6 even if that
>> slows down the final release of Groovy 3.0 and delays further work on
>> better support for JDK9+.
>>
>>
>>
>> Option 2: please release one more alpha of 2.6 over the next month or so
>> which will become the best version to use to assist porting for users stuck
>> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
>> though we will consider PRs from the community for critical fixes.
>>
>>
>>
>> Feedback welcome.
>>
>>
>>
>> Cheers, Paul.
>>
>>
>>
>>
>>
>>
>>
> --
>
> Best regards / Med venlig hilsen,
>
> Søren Berg Glasius
>
> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
> Mobile: +45 40 44 91 88, Skype: sbglasius
> --- Press ESC once to quit - twice to save the changes.
>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Robert Oschwald]

Same with me. Option 3 seems best, even when some of our projects are still on 
Grails 2.


> Am 13.06.2018 um 09:50 schrieb Søren Berg Glasius :
> 
> While the project I'm on is still on JDK 7, but due to Grails 2.x I think 
> that option 3 is the best way to move forward (and nudge projects on to a 
> higher version of Grails as well). 
> 
> /Søren 
> 
> On Wed, 13 Jun 2018, 09.42 ,  > wrote:
> I agree on option 3 (abandon 2.6 immediately). 
> 
>  
> 
> JDK 6 or 7 is not in use anywhere that I have project visibility.
> 
>  
> 
> Full support for JKD9+ is becoming a pressing issue. Users are concerned 
> about the ability of Groovy to run on future JDK releases (including 
> GraalVM), more than legacy support. 
> 
>  
> 
> Best Regards
> 
>  
> 
> From: Paolo Di Tommaso [mailto:paolo.ditomm...@gmail.com 
> ] 
> Sent: Wednesday, June 13, 2018 3:18 AM
> To: users@groovy.apache.org 
> Subject: Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0
> 
>  
> 
> I agree on option 3 (abandon 2.6 immediately). 
> 
>  
> 
> Full support for JKD9+ is becoming a pressing issue. Users are concerned 
> about the ability of Groovy to run on future JDK releases (including 
> GraalVM), more than legacy support. 
> 
>  
> 
>  
> 
> Cheers,
> 
> p
> 
>  
> 
> On Wed, Jun 13, 2018 at 9:11 AM, David Dawson 
>  > wrote:
> 
> I would vote 2.
> 
>  
> 
> Actually, i would vote 3) abandon 2.6 immediately.
> 
>  
> 
> No projects I have any knowledge of still use jdk 7.
> 
>  
> 
> From: pa...@asert.com.au 
> Sent: 13 June 2018 08:06
> 
> To: users@groovy.apache.org 
> Reply to: users@groovy.apache.org 
> Subject: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0
> 
>  
> 
>  
> 
> Hi everyone,
> 
>  
> 
> There was some discussion at gr8conf about how to speed up delivery of Groovy 
> 3.0. Some of that discussion was around the scope of what we want to include 
> and have yet to complete in 3.0 but I won't discuss that right now.
> 
>  
> 
> One of the other discussion points was Groovy around 2.6. As many of you 
> know, we have released alpha versions of Groovy 2.6. That version is a 
> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot 
> parser (though it isn't enabled by default). The purpose of this version has 
> always been to assist people/projects wanting to use the Parrot parser but 
> who might be stuck on JDK7. So in some sense it is an intermediate version to 
> assist with porting towards Groovy 3.0. While that is still a noble goal in 
> theory, in practice, many of our users are already on JDK8 and we have 
> limited resources to work on many potential areas.
> 
>  
> 
> With that in mind, we'd like to understand the preferences in our user base 
> for the following two options:
> 
>  
> 
> Option 1: please continue releasing the best possible 2.6 even if that slows 
> down the final release of Groovy 3.0 and delays further work on better 
> support for JDK9+.
> 
>  
> 
> Option 2: please release one more alpha of 2.6 over the next month or so 
> which will become the best version to use to assist porting for users stuck 
> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired 
> though we will consider PRs from the community for critical fixes.
> 
>  
> 
> Feedback welcome.
> 
>  
> 
> Cheers, Paul.
> 
>  
> 
>  
> 
>  
> 
> -- 
> Best regards / Med venlig hilsen,
> 
> Søren Berg Glasius
> 
> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
> Mobile: +45 40 44 91 88, Skype: sbglasius
> --- Press ESC once to quit - twice to save the changes.
> 

Re: AST to replace `==` with `equals` method invocation

[Mario Garcia]

Hi Paolo:

A couple of years ago I created Asteroid (
https://github.com/grooviter/asteroid) a library to deal with AST
transformations. I needed to create a minor release so I've taken the
oportunity to solve this problem and I think is pretty easy.

   - Create a Transformer. A transformer is just a class transforming a
   specific type of node, and it uses a criteria to filter nodes.
   - Create a Global transformation that includes the previous transformer
   to apply it to the whole codebase
   - Test that the AST generated has changed from a BinaryExpression to a
   MethodCallExpression
   - Profit :)

You can find the source code here:

   - Transformer:
   
https://github.com/grooviter/asteroid/blob/master/asteroid-test/src/main/groovy/asteroid/global/samples/ChangeEqualsTransformer.groovy

   - Transformation:
   
https://github.com/grooviter/asteroid/blob/master/asteroid-test/src/main/groovy/asteroid/global/samples/ChangeEqualsTransformation.groovy
   - Test:
   
https://github.com/grooviter/asteroid/blob/master/asteroid-test/src/test/groovy/asteroid/global/samples/ChangeEqualsTransformationSpec.groovy

You can find also some documentation at:
http://grooviter.github.io/asteroid/

Of course any feedback on the library is appreciated :)

I hope this helps
Mario

2018-06-10 21:27 GMT+02:00 MG :

> Hi Paolo,
>
> I have not used it myself, but have you had a look at the new Groovy 2.5
> "abstract syntax tree search and replace"-feature (http://groovy-lang.org/
> releasenotes/groovy-2.5.html & search for "AST matching") ?
>
> Cheers,
> mg
>
>
>
> On 10.06.2018 16:55, Paolo Di Tommaso wrote:
>
> Dear all,
>
> I'm trying to implement an AST transformation to replace any `==` binary
> expression with a equals method call invocation as suggested here
> 
> .
>
>
> My understanding is that it's required to override each the visitor for
> each node where a binary expression can appear ie. if statement, while
> statement, assignment, for loop, method call, etc.
>
> That looks a bit overkill. I was wondering if there's a better way to
> replace globally all `==` binary expressions with `equals` method
> invocations.
>
>
> Cheers,
> Paolo
>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Søren Berg Glasius]

While the project I'm on is still on JDK 7, but due to Grails 2.x I think
that option 3 is the best way to move forward (and nudge projects on to a
higher version of Grails as well).

/Søren

On Wed, 13 Jun 2018, 09.42 ,  wrote:

> I agree on option 3 (abandon 2.6 immediately).
>
>
>
> JDK 6 or 7 is not in use anywhere that I have project visibility.
>
>
>
> Full support for JKD9+ is becoming a pressing issue. Users are concerned
> about the ability of Groovy to run on future JDK releases (including
> GraalVM), more than legacy support.
>
>
>
> Best Regards
>
>
>
> *From:* Paolo Di Tommaso [mailto:paolo.ditomm...@gmail.com]
> *Sent:* Wednesday, June 13, 2018 3:18 AM
> *To:* users@groovy.apache.org
> *Subject:* Re: [DISCUSS] Groovy 2.6 potential retirement to focus on
> Groovy 3.0
>
>
>
> I agree on option 3 (abandon 2.6 immediately).
>
>
>
> Full support for JKD9+ is becoming a pressing issue. Users are concerned
> about the ability of Groovy to run on future JDK releases (including
> GraalVM), more than legacy support.
>
>
>
>
>
> Cheers,
>
> p
>
>
>
> On Wed, Jun 13, 2018 at 9:11 AM, David Dawson <
> david.daw...@simplicityitself.com> wrote:
>
> I would vote 2.
>
>
>
> Actually, i would vote 3) abandon 2.6 immediately.
>
>
>
> No projects I have any knowledge of still use jdk 7.
>
>
>
> *From:* pa...@asert.com.au
>
> *Sent:* 13 June 2018 08:06
>
> *To:* users@groovy.apache.org
>
> *Reply to:* users@groovy.apache.org
>
> *Subject:* [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy
> 3.0
>
>
>
>
>
> Hi everyone,
>
>
>
> There was some discussion at gr8conf about how to speed up delivery of
> Groovy 3.0. Some of that discussion was around the scope of what we want to
> include and have yet to complete in 3.0 but I won't discuss that right now.
>
>
>
> One of the other discussion points was Groovy around 2.6. As many of you
> know, we have released alpha versions of Groovy 2.6. That version is a
> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
> parser (though it isn't enabled by default). The purpose of this version
> has always been to assist people/projects wanting to use the Parrot parser
> but who might be stuck on JDK7. So in some sense it is an intermediate
> version to assist with porting towards Groovy 3.0. While that is still a
> noble goal in theory, in practice, many of our users are already on JDK8
> and we have limited resources to work on many potential areas.
>
>
>
> With that in mind, we'd like to understand the preferences in our user
> base for the following two options:
>
>
>
> Option 1: please continue releasing the best possible 2.6 even if that
> slows down the final release of Groovy 3.0 and delays further work on
> better support for JDK9+.
>
>
>
> Option 2: please release one more alpha of 2.6 over the next month or so
> which will become the best version to use to assist porting for users stuck
> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
> though we will consider PRs from the community for critical fixes.
>
>
>
> Feedback welcome.
>
>
>
> Cheers, Paul.
>
>
>
>
>
>
>
-- 

Best regards / Med venlig hilsen,

Søren Berg Glasius

Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.

RE: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[William.W.Mangum]

I agree on option 3 (abandon 2.6 immediately).

JDK 6 or 7 is not in use anywhere that I have project visibility.

Full support for JKD9+ is becoming a pressing issue. Users are concerned about 
the ability of Groovy to run on future JDK releases (including GraalVM), more 
than legacy support.

Best Regards

From: Paolo Di Tommaso [mailto:paolo.ditomm...@gmail.com]
Sent: Wednesday, June 13, 2018 3:18 AM
To: users@groovy.apache.org
Subject: Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

I agree on option 3 (abandon 2.6 immediately).

Full support for JKD9+ is becoming a pressing issue. Users are concerned about 
the ability of Groovy to run on future JDK releases (including GraalVM), more 
than legacy support.


Cheers,
p

On Wed, Jun 13, 2018 at 9:11 AM, David Dawson 
mailto:david.daw...@simplicityitself.com>> 
wrote:
I would vote 2.

Actually, i would vote 3) abandon 2.6 immediately.

No projects I have any knowledge of still use jdk 7.

From: pa...@asert.com.au
Sent: 13 June 2018 08:06
To: users@groovy.apache.org
Reply to: users@groovy.apache.org
Subject: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0



Hi everyone,

There was some discussion at gr8conf about how to speed up delivery of Groovy 
3.0. Some of that discussion was around the scope of what we want to include 
and have yet to complete in 3.0 but I won't discuss that right now.

One of the other discussion points was Groovy around 2.6. As many of you know, 
we have released alpha versions of Groovy 2.6. That version is a backport of 
most but not all of Groovy 3.0 to JDK7 including the Parrot parser (though it 
isn't enabled by default). The purpose of this version has always been to 
assist people/projects wanting to use the Parrot parser but who might be stuck 
on JDK7. So in some sense it is an intermediate version to assist with porting 
towards Groovy 3.0. While that is still a noble goal in theory, in practice, 
many of our users are already on JDK8 and we have limited resources to work on 
many potential areas.

With that in mind, we'd like to understand the preferences in our user base for 
the following two options:

Option 1: please continue releasing the best possible 2.6 even if that slows 
down the final release of Groovy 3.0 and delays further work on better support 
for JDK9+.

Option 2: please release one more alpha of 2.6 over the next month or so which 
will become the best version to use to assist porting for users stuck on JDK7 
and then focus on 3.0. The 2.6 branch will essentially be retired though we 
will consider PRs from the community for critical fixes.

Feedback welcome.

Cheers, Paul.

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Paolo Di Tommaso]

I agree on option 3 (abandon 2.6 immediately).

Full support for JKD9+ is becoming a pressing issue. Users are concerned
about the ability of Groovy to run on future JDK releases (including
GraalVM), more than legacy support.


Cheers,
p

On Wed, Jun 13, 2018 at 9:11 AM, David Dawson <
david.daw...@simplicityitself.com> wrote:

> I would vote 2.
>
> Actually, i would vote 3) abandon 2.6 immediately.
>
> No projects I have any knowledge of still use jdk 7.
>
> *From:* pa...@asert.com.au
> *Sent:* 13 June 2018 08:06
> *To:* users@groovy.apache.org
> *Reply to:* users@groovy.apache.org
> *Subject:* [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy
> 3.0
>
>
> Hi everyone,
>
> There was some discussion at gr8conf about how to speed up delivery of
> Groovy 3.0. Some of that discussion was around the scope of what we want to
> include and have yet to complete in 3.0 but I won't discuss that right now.
>
> One of the other discussion points was Groovy around 2.6. As many of you
> know, we have released alpha versions of Groovy 2.6. That version is a
> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
> parser (though it isn't enabled by default). The purpose of this version
> has always been to assist people/projects wanting to use the Parrot parser
> but who might be stuck on JDK7. So in some sense it is an intermediate
> version to assist with porting towards Groovy 3.0. While that is still a
> noble goal in theory, in practice, many of our users are already on JDK8
> and we have limited resources to work on many potential areas.
>
> With that in mind, we'd like to understand the preferences in our user
> base for the following two options:
>
> Option 1: please continue releasing the best possible 2.6 even if that
> slows down the final release of Groovy 3.0 and delays further work on
> better support for JDK9+.
>
> Option 2: please release one more alpha of 2.6 over the next month or so
> which will become the best version to use to assist porting for users stuck
> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
> though we will consider PRs from the community for critical fixes.
>
> Feedback welcome.
>
> Cheers, Paul.
>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Alessio Stalla]

2 for me as well.

Il mer 13 giu 2018, 09:11 David Dawson 
ha scritto:

> I would vote 2.
>
> Actually, i would vote 3) abandon 2.6 immediately.
>
> No projects I have any knowledge of still use jdk 7.
>
> *From:* pa...@asert.com.au
> *Sent:* 13 June 2018 08:06
> *To:* users@groovy.apache.org
> *Reply to:* users@groovy.apache.org
> *Subject:* [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy
> 3.0
>
>
> Hi everyone,
>
> There was some discussion at gr8conf about how to speed up delivery of
> Groovy 3.0. Some of that discussion was around the scope of what we want to
> include and have yet to complete in 3.0 but I won't discuss that right now.
>
> One of the other discussion points was Groovy around 2.6. As many of you
> know, we have released alpha versions of Groovy 2.6. That version is a
> backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
> parser (though it isn't enabled by default). The purpose of this version
> has always been to assist people/projects wanting to use the Parrot parser
> but who might be stuck on JDK7. So in some sense it is an intermediate
> version to assist with porting towards Groovy 3.0. While that is still a
> noble goal in theory, in practice, many of our users are already on JDK8
> and we have limited resources to work on many potential areas.
>
> With that in mind, we'd like to understand the preferences in our user
> base for the following two options:
>
> Option 1: please continue releasing the best possible 2.6 even if that
> slows down the final release of Groovy 3.0 and delays further work on
> better support for JDK9+.
>
> Option 2: please release one more alpha of 2.6 over the next month or so
> which will become the best version to use to assist porting for users stuck
> on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
> though we will consider PRs from the community for critical fixes.
>
> Feedback welcome.
>
> Cheers, Paul.
>
>
>

Re: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[David Dawson]

  I would vote 2.Actually, i would vote 3) abandon 2.6 immediately.No projects I have any knowledge of still use jdk 7.   From: pa...@asert.com.auSent: 13 June 2018 08:06To: users@groovy.apache.orgReply to: users@groovy.apache.orgSubject: [DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0  Hi everyone,There was some discussion at gr8conf about how to speed up delivery of Groovy 3.0. Some of that discussion was around the scope of what we want to include and have yet to complete in 3.0 but I won't discuss that right now.One of the other discussion points was Groovy around 2.6. As many of you know, we have released alpha versions of Groovy 2.6. That version is a backport of most but not all of Groovy 3.0 to JDK7 including the Parrot parser (though it isn't enabled by default). The purpose of this version has always been to assist people/projects wanting to use the Parrot parser but who might be stuck on JDK7. So in some sense it is an intermediate version to assist with porting towards Groovy 3.0. While that is still a noble goal in theory, in practice, many of our users are already on JDK8 and we have limited resources to work on many potential areas.With that in mind, we'd like to understand the preferences in our user base for the following two options:Option 1: please continue releasing the best possible 2.6 even if that slows down the final release of Groovy 3.0 and delays further work on better support for JDK9+.Option 2: please release one more alpha of 2.6 over the next month or so which will become the best version to use to assist porting for users stuck on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired though we will consider PRs from the community for critical fixes.Feedback welcome.Cheers, Paul.

[DISCUSS] Groovy 2.6 potential retirement to focus on Groovy 3.0

[Paul King]

Hi everyone,

There was some discussion at gr8conf about how to speed up delivery of
Groovy 3.0. Some of that discussion was around the scope of what we want to
include and have yet to complete in 3.0 but I won't discuss that right now.

One of the other discussion points was Groovy around 2.6. As many of you
know, we have released alpha versions of Groovy 2.6. That version is a
backport of most but not all of Groovy 3.0 to JDK7 including the Parrot
parser (though it isn't enabled by default). The purpose of this version
has always been to assist people/projects wanting to use the Parrot parser
but who might be stuck on JDK7. So in some sense it is an intermediate
version to assist with porting towards Groovy 3.0. While that is still a
noble goal in theory, in practice, many of our users are already on JDK8
and we have limited resources to work on many potential areas.

With that in mind, we'd like to understand the preferences in our user base
for the following two options:

Option 1: please continue releasing the best possible 2.6 even if that
slows down the final release of Groovy 3.0 and delays further work on
better support for JDK9+.

Option 2: please release one more alpha of 2.6 over the next month or so
which will become the best version to use to assist porting for users stuck
on JDK7 and then focus on 3.0. The 2.6 branch will essentially be retired
though we will consider PRs from the community for critical fixes.

Feedback welcome.

Cheers, Paul.