Hi Cédric,
If possible, how about providing the new parser via putting it in a
separate artifact(e.g. groovy-parser-x.x.x.jar). When Groovy developers want
to try the new parser, they can enable the switch(-Dgroovy.antlr4=true).
Before set the new parser as the default parser in the future r
On 20.10.2016 10:31, Cédric Champeau wrote:
I would much favor letting the 2.4 branch die (aka, release 2.4.8), then
make 2.5-beta and final asap, and release regular 3.0 milestones.
I think that is too early to decide right now. Because right now we need
to release 2.4.8 and 2.5.0-beta-1. And
I would much favor letting the 2.4 branch die (aka, release 2.4.8), then
make 2.5-beta and final asap, and release regular 3.0 milestones.
2016-10-20 10:29 GMT+02:00 Jochen Theodorou :
> On 20.10.2016 09:28, Cédric Champeau wrote:
>
>> I don't think it's reasonable to put the new parser in 2.5. T
On 20.10.2016 09:28, Cédric Champeau wrote:
I don't think it's reasonable to put the new parser in 2.5. There are
too many grey areas: performance, backwards compatibility, dependencies,
upgrade to Java 8... Better ship 2.5, then work hard on 3.0, even if it
means delaying MOP2 to 4.0.
first of
I don't think it's reasonable to put the new parser in 2.5. There are too
many grey areas: performance, backwards compatibility, dependencies,
upgrade to Java 8... Better ship 2.5, then work hard on 3.0, even if it
means delaying MOP2 to 4.0.
2016-10-20 1:52 GMT+02:00 Jochen Theodorou :
> On 19.1
On 19.10.2016 18:11, Mario Garcia wrote:
Does anyone have any idea of how long is going to take the new parser to
be ready ? It's a matter of weeks, months, maybe days? I think that
information would help to plan future releases.
I just made an experiment in which I moved the antlr2 parser in i
Mario, did you try the WIP by Daniel Sun, to provide feedback, see how it
works on your code base?
That's also a way to help and assess how far we are from having the new
parser ready, if you've got a bit of time to try it out.
On Wed, Oct 19, 2016 at 6:11 PM, Mario Garcia wrote:
> +1 for releas
+1 for releasing 2.4.8 asap
Does anyone have any idea of how long is going to take the new parser to be
ready ? It's a matter of weeks, months, maybe days? I think that
information would help to plan future releases.
Mario
On 19 Oct 2016 17:15, "Pascal Schumacher" wrote:
> +1 for releasing 2.4
+1 for releasing 2.4.8 as soon as possible. There are already 67 fixed
issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20%3D%202.4.8%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC
Am 19.10.2016 um 16:32 schrieb Jochen Theodorou:
Hi,
I´dd like to
If we could get a fix for https://issues.apache.org/jira/browse/GROOVY-7966,
it would help Gradle, because it prevents our caching from working without
a hack (basically sorting files, which has a performance cost).
2016-10-19 16:32 GMT+02:00 Jochen Theodorou :
> Hi,
>
> I´dd like to collect here
Hi,
I´dd like to collect here a list of things we have to do to get the next
2.4 and the first beta of 2.5.0 out. I do not know of any criticals for
2.4.x, so afaik it is ready for release any time now. For 2.5.0 I see
the following we should integrate the new parser (could be done for
2.4.x
11 matches
Mail list logo
