Re: Recommended groupId for external Groovy modules

2016-12-28 Thread Guillaume Laforge
Hi Marcin, Some modules have used the groovyx.* namespace in the past. It's somewhat semi-standard, in the sense that it's already in use, at least. It's not dependent upon Apache or the defunct Codehaus foundation, and there's no constraint from Sonatype on those. If using groovyx, it'd be good t

ready for 2.4.8?

2016-12-28 Thread Paul King
Hi everyone, I am ready to push out a 2.4.8 release. Any other last minute changes that need to be done? If I don't hear anything further, I'll do the first steps for the release (my) tomorrow and prepare some candidate artefacts and a [VOTE] thread. Cheers, Paul.

Re: ready for 2.4.8?

2016-12-28 Thread Andres Almiray
Wondering if https://issues.apache.org/jira/browse/GROOVY-7472 was applied to the 2.4.x branch. It appears to be fixed for 2.5.x. Would be great to have it in 2.4.8. It's an innocuous feature however I've found myself needing it a couple of times already in the past months. Cheers, Andres --

Re: Recommended groupId for external Groovy modules

2016-12-28 Thread Marcin ZajÄ…czkowski
On 2016-12-28 11:49, Guillaume Laforge wrote: > Hi Marcin, > > Some modules have used the groovyx.* namespace in the past. > It's somewhat semi-standard, in the sense that it's already in use, at > least. > It's not dependent upon Apache or the defunct Codehaus foundation, and > there's no constra