Re: release process

2017-01-20 Thread Jochen Theodorou
On 19.01.2017 20:07, Paul King wrote: +1 with a few comments below. There has been discussion about releases for 2.4.9, 2.5.0-beta-1 and 3.0.0-ea-1. Perhaps we should split between us? I'd suggest I do the first two with you as "co-pilot" and swap roles for the third? the first two time-wise

Re: The order of modifiers and annotations

2017-01-20 Thread Marcin Erdmann
Awesome! On Thu, Jan 19, 2017 at 11:01 AM, Daniel Sun wrote: > I verified that the new parser Parrot does not have the issue( GROOVY-4757 > ), the following test > case was added in the parrot branch. And I'll resolve the JIRA issue later. > >

Re: The order of modifiers and annotations

2017-01-20 Thread Daniel Sun
Thanks :) 在 "Marcin Erdmann [via Groovy]" ，2017年1月20日 下午5:09写道： Awesome! On Thu, Jan 19, 2017 at 11:01 AM, Daniel Sun <[hidden email]> wrote: I verified that the new parser Parrot does not have the issue( GROOVY-4757 ), the following test c

Re: release process

2017-01-20 Thread Paul King
Wasn't the consensus to have parrot just in 3.0? So we could make the 2_5_X branch now? On 20 Jan 2017 8:08 PM, "Jochen Theodorou" wrote: > > > On 19.01.2017 20:07, Paul King wrote: > >> +1 with a few comments below. >> >> There has been discussion about releases for 2.4.9, 2.5.0-beta-1 and >> 3

Re: release process

2017-01-20 Thread Jochen Theodorou
On 20.01.2017 13:14, Paul King wrote: Wasn't the consensus to have parrot just in 3.0? So we could make the 2_5_X branch now? may have missed something like a consensus I guess. But frankly I don´t get why parrot should not even be optional in 2.5.x. bye Jochen

Re: release process

2017-01-20 Thread Paul King
The concern was added complexity but maybe it isn't much different to normal. From my side, I need to play around some more to confirm either way. At a minimum, we'd need to use java 8 to do the 2.5.x releases, and have something sensible built, i.e. without the parrot option, for those compiling

Re: release process

2017-01-20 Thread Cédric Champeau
Let me rephrase what I said. My concern is not about complexity. My concern is that parrot is an experimental parser, that requires Java 8, and an additional dependency, antlr4, which conflicts with an existing dependency, antlr2. I don't want to mix things like that. The new parser should be, as a

Re: release process

2017-01-20 Thread Jochen Theodorou
On 20.01.2017 22:04, Cédric Champeau wrote: Let me rephrase what I said. My concern is not about complexity. My concern is that parrot is an experimental parser, that requires Java 8, and an additional dependency, antlr4, which conflicts with an existing dependency, antlr2. antlr2 and antrl4 ar

Re: MavenGrapeEngine?

2017-01-20 Thread Sergei Egorov
FYI https://github.com/igor-suhorukov/mvn-classloader On Tue, Jan 10, 2017 at 11:43 AM Romain Manni-Bucau wrote: > Hmm, ibiblio (localm2 in grapesConfig.xml) has setChangingPattern( > ".*-SNAPSHOT"); so should have worked OOTBbut > > org.apache.ivy.plugins.resolver.ChainResolver#getDependenc