Re: [VOTE] Release Groovy 2.4.8 - take 3

2017-01-10 Thread jim northrop
Thank you Paul. We're working to get GPars V2.0 doc.s ready so will include 2.4.8 plus asciidoctor 1.5.5 just out this morning. ☺️ Sent from my iPad > On 11 Jan 2017, at 01:42, Paul King wrote: > > A little early to give an exact ETA Jim. I'll update here when I know more. > > On Wed, Jan 11,

Re: [VOTE] Release Groovy 2.4.8

2017-01-10 Thread Roman Shaposhnik
On Tue, Jan 10, 2017 at 5:02 AM, Paul King wrote: > Looks like everyone is keen to get the release out soon. Given it was > just a minor tweak to the build file, I'll re-issue the vote but with > a 48 hr window. +1 Thanks, Roman.

Re: [VOTE] Release Groovy 2.4.8 - take 3

2017-01-10 Thread Paul King
A little early to give an exact ETA Jim. I'll update here when I know more. On Wed, Jan 11, 2017 at 2:05 AM, Jim Northrop wrote: > Do we have an ETA date when we can chg our gradle configs to pull 2.4.8 > please? > > Sent from my iPad > >> On 10 Jan 2017, at 14:06, Paul King wrote: >> >> [Hopef

Re: [VOTE] Release Groovy 2.4.8 - take 3

2017-01-10 Thread Jim Northrop
Do we have an ETA date when we can chg our gradle configs to pull 2.4.8 please? Sent from my iPad > On 10 Jan 2017, at 14:06, Paul King wrote: > > [Hopefully for real this time] > > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.4.8 release! > > This release includes

Re: [VOTE] Release Groovy 2.4.8 - take 3

2017-01-10 Thread Cédric Champeau
+1 (binding) Checking apache-groovy-src-2.4.8.zip : signature [ok] checksum [ok] Checking apache-groovy-binary-2.4.8.zip : signature [ok] checksum [ok] Checking apache-groovy-sdk-2.4.8.zip : signature [ok] checksum [ok] Checking apache-groovy-docs-2.4.8.zip : signature [ok] checksum [ok] 2017-01

Re: [VOTE] Release Groovy 2.4.8 - take 3

2017-01-10 Thread Jochen Theodorou
+1 On 10.01.2017 14:10, Guillaume Laforge wrote: +1 (binding) On Tue, Jan 10, 2017 at 2:06 PM, Paul King mailto:pa...@asert.com.au>> wrote: [Hopefully for real this time] Dear community, I am happy to start the VOTE thread for a Groovy 2.4.8 release! This release includes 85

Re: [VOTE] Release Groovy 2.4.8 - take 3

2017-01-10 Thread Guillaume Laforge
+1 (binding) On Tue, Jan 10, 2017 at 2:06 PM, Paul King wrote: > [Hopefully for real this time] > > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.4.8 release! > > This release includes 85 bug fixes/improvements as outlined in the > changelog: > https://issues.apache.org/

[VOTE] Release Groovy 2.4.8 - take 3

2017-01-10 Thread Paul King
[Hopefully for real this time] Dear community, I am happy to start the VOTE thread for a Groovy 2.4.8 release! This release includes 85 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12335950 Tag: https://g

Re: [VOTE] Release Groovy 2.4.8

2017-01-10 Thread Paul King
Looks like everyone is keen to get the release out soon. Given it was just a minor tweak to the build file, I'll re-issue the vote but with a 48 hr window. On Tue, Jan 10, 2017 at 10:39 PM, Cédric Champeau wrote: > If the difference is just in fixing the build, maybe a shorter vote is > acceptabl

Re: [VOTE] Release Groovy 2.4.8

2017-01-10 Thread Cédric Champeau
If the difference is just in fixing the build, maybe a shorter vote is acceptable? 2017-01-10 13:37 GMT+01:00 Uwe Schindler : > Hi, > > > > This also delays fixing Lucene‘s build system for our release Lucene 6.4, > so we can test Java 9 build 148+. So it’s a pity! > > > > Uwe > > > > - > > U

Re: [VOTE] Release Groovy 2.4.8

2017-01-10 Thread Guillaume Laforge
I also believe it's okay, and not critical, leading us to cancel the vote. We can just list that point as a known (minor) issue. On Tue, Jan 10, 2017 at 12:41 PM, Cédric Champeau wrote: > Was it such a big deal we needed to cancel the vote? I find it a bit > unfortunate, since "building" just wo

RE: [VOTE] Release Groovy 2.4.8

2017-01-10 Thread Uwe Schindler
Hi, This also delays fixing Lucene‘s build system for our release Lucene 6.4, so we can test Java 9 build 148+. So it’s a pity! Uwe - Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de From: Cédric Champeau

Re: [VOTE] Release Groovy 2.4.8

2017-01-10 Thread Cédric Champeau
Was it such a big deal we needed to cancel the vote? I find it a bit unfortunate, since "building" just works, or that setting the signing properties do. Anyway I leave it to you. 2017-01-10 12:37 GMT+01:00 Paul King : > John found an issue with "install" if you don't have signing properties in >

Re: [VOTE] Release Groovy 2.4.8

2017-01-10 Thread Paul King
John found an issue with "install" if you don't have signing properties in place. As painful as it is, I'll cancel the vote and try again. I have re-run the tweaked build script and the new artifacts are re-uploaded to the same place on the DEV server. Anyone want to give it a quick try before I d

Re: MavenGrapeEngine?

2017-01-10 Thread Romain Manni-Bucau
Hmm, ibiblio (localm2 in grapesConfig.xml) has setChangingPattern( ".*-SNAPSHOT"); so should have worked OOTBbut org.apache.ivy.plugins.resolver.ChainResolver#getDependency checks the ivy (default) cache before using resolvers so resolvers are basically skipped and even the localm2 good behavi

Re: MavenGrapeEngine?

2017-01-10 Thread Paul King
Perhaps something can be done but some people use snapshots without any timestamps. As long as that didn't break. I think years ago it became a lot slower in that scenario if we auto set 'changing'. Not sure if that is the case any longer. Cheers, Paul. On Tue, Jan 10, 2017 at 6:48 PM, Romain Man

Re: MavenGrapeEngine?

2017-01-10 Thread Romain Manni-Bucau
Ok, imported the project and...discovered changing() :). Think it can solve the issue for now. Then the remaining question is the duplication of the repo but guess I can live with it for now. In GrapeIvy do we want to move boolean changing = deps.containsKey('changing') ? deps.changing : fal