groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Winnebeck, Jason" <>
Subject RE: Groovy Beta
Date Fri, 15 Jan 2016 19:46:48 GMT
I have built Groovy on my home machine successfully, it is not bad at all. However, I'm working
on a large enterprise app, so it is nice to at least have some form of snapshot in time. So,
I can deploy it to our local Maven repository under different group ID, but then I still have
the uncertainty of pulling the latest code and not even knowing if there is a half-finished
task or refactor going on in there, whereas with a "blessed" beta the team is saying they
think the code is clean. I could validate the "tip" works in our app but that is not productive
if a release is coming soon. There's also the awkward-ness of having a custom-built Groovy
not-quite-2.4 but not-quite-2.5 version out and about. However, the fix is big enough for
me that if it doesn't make it into the recent 2.4.6 release, I may very well go through the
effort to build the tip of beta branch and validate.


-----Original Message-----
From: Russel Winder [] 
Sent: Friday, January 15, 2016 2:29 PM
Subject: Re: Groovy Beta

On Fri, 2016-01-15 at 19:05 +0000, Winnebeck, Jason wrote:
> A Groovy issue that affects us significantly was recently fixed in the 
> Apache JIRA as "2.5.0-beta1". From what I can tell, there is not 
> currently a place to download betas. Is there a plan to release a 
> Groovy 2.5 beta milestoon soon?

Probably not. I compile and install from source. Takes about 22 mins on my workstation (which
is 9 years old so I expect modern kit to do better).

Dr Russel Winder      t: +44 20 7585 2200   voip:
41 Buckmaster Road    m: +44 7770 465 077   xmpp:
London SW11 1EN, UK   w:  skype: russel_winder

This email message and any attachments are for the sole use of the intended recipient(s).
Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy all copies of the
original message and any attachments.
View raw message