Hi Jan,
I just merged PR#923, thanks for your contribution.
P.S.
1) I have not noticed that you have tweaked the PR according to the
discussion with Paul. Long overdue...
2) I will try to cherry-pick the PR#923 for 2.5 branch, so PR#924 is not
merged.
Cheers,
Daniel.Sun
-
Apache Gr
Hello Daniel,
would it be possible to include these two small PRs?
https://github.com/apache/groovy/pull/923
https://github.com/apache/groovy/pull/924
Many thanks!
Jan
On 7/29/19 12:37 PM, Daniel.Sun wrote:
As more important fixes are targeted to the two releases, the dual releases
will be
As more important fixes are targeted to the two releases, the dual releases
will be postponed to next week.
Cheers,
Daniel.Sun
-
Apache Groovy committer & PMC member
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.htm
*To:* Groovy_Developers
> *Subject:* Re: Apache Groovy 3.0.0-beta-3 and 2.5.8 are coming
>
>
> Sounds good. My current planning for rc-1 is in about a month from now. I
> will also create a branch for 3 and make master ready for 4 at that time.
>
> What remains for 3 GA is to move ac
Is there a quick way to determine what items are being fixed in 2.5 and 3.0?
I'd like to see if 2.5 got ports of as many bug fixes as possible.
From: Paul King
Sent: Friday, July 19, 2019 5:04 AM
To: Groovy_Developers
Subject: Re: Apache Groovy 3.0.0-b
before looking further.
From: Andres Almiray
Sent: Friday, July 19, 2019 5:16 AM
To: dev@groovy.apache.org; Paul King
Subject: Re: Apache Groovy 3.0.0-beta-3 and 2.5.8 are coming
I wish we could find a fix for
https://issues.apache.org/jira/projects/GROOVY/iss
+1
I can help, I'll need some directions on where to start but I think I can
do it.
cheers.
Mauricio.
On Fri, Jul 19, 2019, 7:04 AM Paul King wrote:
>
> Sounds good. My current planning for rc-1 is in about a month from now. I
> will also create a branch for 3 and make master ready for 4 at t
I wish we could find a fix for
https://issues.apache.org/jira/projects/GROOVY/issues/GROOVY-9199?filter=allopenissues
It appears there's a regression between 2.5.4 and 2.5.5 that's been carried
over to 2.5.7.
Unfortunately I don't have the bytecode knowledge to fix this one myself :'(
Cheers,
An
Sounds good. My current planning for rc-1 is in about a month from now. I
will also create a branch for 3 and make master ready for 4 at that time.
What remains for 3 GA is to move across as many of the tools as possible
that are still using the old grammar onto the new grammar (this includes
groo
