Return-Path: X-Original-To: apmail-groovy-users-archive@minotaur.apache.org Delivered-To: apmail-groovy-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5F56418183 for ; Fri, 15 Jan 2016 23:04:52 +0000 (UTC) Received: (qmail 55328 invoked by uid 500); 15 Jan 2016 23:04:52 -0000 Delivered-To: apmail-groovy-users-archive@groovy.apache.org Received: (qmail 55297 invoked by uid 500); 15 Jan 2016 23:04:52 -0000 Mailing-List: contact users-help@groovy.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@groovy.apache.org Delivered-To: mailing list users@groovy.apache.org Received: (qmail 55287 invoked by uid 99); 15 Jan 2016 23:04:52 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jan 2016 23:04:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B7670C0F2F for ; Fri, 15 Jan 2016 23:04:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id MLiC5oYKBCvO for ; Fri, 15 Jan 2016 23:04:38 +0000 (UTC) Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 83D0E20520 for ; Fri, 15 Jan 2016 23:04:38 +0000 (UTC) Received: by mail-ig0-f182.google.com with SMTP id t15so22062939igr.0 for ; Fri, 15 Jan 2016 15:04:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=FejCLcWYQqJrp+iDWLUd5ElaCW9PkSf+1iBVbZIT27E=; b=paipM10eWFd6qnSJ2uOPJmhW84t4h3bXFyiRXSdz8H9o4IlIlE0fx5N6MpJfDghH/S I8M+1QasiMLFBhrAXo9nDel8DV8yJR3AK0EURmNXSS4cPK8aWbTqiNX10prckbZrssYc WV1eZDQvS8tw5BaJPV3hNKehnVdGwTl8XPUtsZo0rs3ZOzXh3IwAc2QnnTwZGXmbYJC1 TxDtfbPTgRh21M5wsupCxgQSLCRwqpr9nAtVG3EfQFxid7b0TFTeUHBV3H6IpCoD9aBk Db84FS6ZEWethVXl6//q2HANMEWQsLog/SM/Tbq+0odxJUrHgO6ivyowuKo76iJCmysJ 3zxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=FejCLcWYQqJrp+iDWLUd5ElaCW9PkSf+1iBVbZIT27E=; b=RAU0AF0lagUcjPZUK7uc3uU/2r1NmCkVeVN3LI0PUSMuDmnC4T1mC1nPa/Blzs+IKb +RPGvxrAxMNDavgC5tnaK2NhvWPxqzSWX8ToKvvDAMAfQN9Lk/qiswGFIa13yxIAONgu 43OqaOCOoyUYIAtkPzU1K2mTAddCzvgDgHqP2BFBMzFCEIqQ25QHTbxg/De1jZVp2quj xvCYk4hkBD6Ko8zA7JT25Z1S5i+wdfvvxZYmO6E7J6VOm+ZfbgAtil/j0z5LrGP2s54l N0fxdHltqViVI80xqnR4J+osBLVT3BC5M8TgCJbtMLxYmv4as3Z1h1AuKDsX/l5zkZt/ oHIA== X-Gm-Message-State: AG10YOSELlaMXzeRP6nNo3QpKA2ltUxxxWvUKiT0TVEaLjLVprEx7++yyOZClV+iDTIxotCWCt/ZGMTwoTB78A== MIME-Version: 1.0 X-Received: by 10.50.60.73 with SMTP id f9mr856722igr.97.1452899077935; Fri, 15 Jan 2016 15:04:37 -0800 (PST) Received: by 10.79.21.197 with HTTP; Fri, 15 Jan 2016 15:04:37 -0800 (PST) In-Reply-To: References: <5C676E6359909E478C7B811BDB48CA3543E954@CWWAPP478.windstream.com> <1452886168.2939.126.camel@winder.org.uk> <5C676E6359909E478C7B811BDB48CA3543E9BD@CWWAPP478.windstream.com> <56994E4A.3050506@gmx.net> <5C676E6359909E478C7B811BDB48CA3543E9F9@CWWAPP478.windstream.com> Date: Fri, 15 Jan 2016 18:04:37 -0500 Message-ID: Subject: Re: Groovy Beta From: Shil Sinha To: users@groovy.apache.org Content-Type: multipart/alternative; boundary=e89a8ffbabdb6f59d60529676de5 --e89a8ffbabdb6f59d60529676de5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I didn't backport the fix for the issue in question because it wasn't a trivial change, and seemed to be more of an enhancement than a bugfix. That being said, I don't feel too strongly about the changes not being in 2.4.X, so I'd be OK with backporting the changes if other committers are for it. On Fri, Jan 15, 2016 at 4:27 PM, C=C3=A9dric Champeau wrote: > Fixes should almost always be backported, unless there's a good reason no= t > to (for example, backporting means rewriting part of the fix). If it's no= t > the case, then it's a mistake. I have not been capable of checking if the > recent fixes on master have been systematically backported, but they > should. So hopefully this is just JIRA not up-to-date. > > 2016-01-15 21:13 GMT+01:00 Winnebeck, Jason < > Jason.Winnebeck@windstream.com>: > >> Sorry, I wasn't clear. By snapshot I meant a declaration/tag by the >> developers. For example when Groovy team releases 2.5.0-beta1, not only = is >> it something I can explain globally "we are using 2.5.0-beta1 and see xy= z", >> but it also means that the team is saying the code is in a reasonable st= ate >> for someone to use (i.e. there's not a major refactor in progress -- for >> example I have no clue if 2.5.0 being a new feature branch has a refacto= r >> going on). >> >> Anyway, knowing about the snapshot builds is useful as I can eliminate >> any potential mistake in my build process. I will try that snapshot JAR >> Monday to verify the fix for GROOVY-7705 for our application. >> >> I apologize about the side-tracked conversation, initially I only meant >> to ask whether or not a release was soon to know if I should go through = the >> effort of validating a nightly for a production system. Since 2.5 beta i= s >> not soon, the only open question left for me is if GROOVY-7705 could be >> backported into 2.4.6 or at least 2.4.x (I'd feel safer with a >> 2.4.7-SNAPSHOT than 2.5.0-SNAPSHOT). I asked that in the JIRA. >> >> -----Original Message----- >> From: Pascal Schumacher [mailto:pascalschumacher@gmx.net] >> Sent: Friday, January 15, 2016 2:54 PM >> To: users@groovy.apache.org >> Subject: Re: Groovy Beta >> >> Hi Jason, >> >> you do not have to build it yourself if you want to validate a snapshot. >> >> You can add https://oss.jfrog.org/artifactory/oss-snapshot-local/ as a >> maven repo and pull 2.5.0-SNAPSHOT from there. >> >> -Pascal >> >> Am 15.01.2016 um 20:46 schrieb Winnebeck, Jason: >> > 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 loc= al >> 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 "blesse= d" >> beta the team is saying they think the code is clean. I could validate t= he >> "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 relea= se, >> I may very well go through the effort to build the tip of beta branch an= d >> validate. >> > >> > Jason >> > >> > -----Original Message----- >> > From: Russel Winder [mailto:russel@winder.org.uk] >> > Sent: Friday, January 15, 2016 2:29 PM >> > To: users@groovy.apache.org >> > 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 o= n >> my workstation (which is 9 years old so I expect modern kit to do better= ). >> > >> > -- >> > Russel. >> > >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >> > Dr Russel Winder t: +44 20 7585 2200 voip: >> sip:russel.winder@ekiga.net >> > 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk >> > London SW11 1EN, UK w: www.russel.org.uk 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, pleas= e >> contact the sender by reply email and destroy all copies of the original >> message and any attachments. >> >> > --e89a8ffbabdb6f59d60529676de5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I didn't backport the fix for the issue in question be= cause it wasn't a trivial change, and seemed to be more of an enhanceme= nt than a bugfix. That being said, I don't feel too strongly about the = changes not being in 2.4.X, so I'd be OK with backporting the changes i= f other committers are for it.

On Fri, Jan 15, 2016 at 4:27 PM, C=C3=A9dric Champeau <cedric.champeau@gmail.com> wrote:
Fixes should almost always be backported, u= nless there's a good reason not to (for example, backporting means rewr= iting part of the fix). If it's not the case, then it's a mistake. = I have not been capable of checking if the recent fixes on master have been= systematically backported, but they should. So hopefully this is just JIRA= not up-to-date.

2016-01-15 21:13 GMT+01:00 Win= nebeck, Jason <Jason.Winnebeck@windstream.com>:=
Sorry, I wasn't clear. By snapshot I= meant a declaration/tag by the developers. For example when Groovy team re= leases 2.5.0-beta1, not only is it something I can explain globally "w= e are using 2.5.0-beta1 and see xyz", but it also means that the team = is saying the code is in a reasonable state for someone to use (i.e. there&= #39;s not a major refactor in progress -- for example I have no clue if 2.5= .0 being a new feature branch has a refactor going on).

Anyway, knowing about the snapshot builds is useful as I can eliminate any = potential mistake in my build process. I will try that snapshot JAR Monday = to verify the fix for GROOVY-7705 for our application.

I apologize about the side-tracked conversation, initially I only meant to = ask whether or not a release was soon to know if I should go through the ef= fort of validating a nightly for a production system. Since 2.5 beta is not= soon, the only open question left for me is if GROOVY-7705 could be backpo= rted into 2.4.6 or at least 2.4.x (I'd feel safer with a 2.4.7-SNAPSHOT= than 2.5.0-SNAPSHOT). I asked that in the JIRA.

-----Original Message-----
From: Pascal Schumacher [mailto:pascalschumacher@gmx.net]
Sent: Friday, January 15, 2016 2:54 PM
To: users@groo= vy.apache.org
Subject: Re: Groovy Beta

Hi Jason,

you do not have to build it yourself if you want to validate a snapshot.
You can add https://oss.jfrog.org/artifactory/o= ss-snapshot-local/ as a maven repo and pull 2.5.0-SNAPSHOT from there.<= br>
-Pascal

Am 15.01.2016 um 20:46 schrieb Winnebeck, Jason:
> 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 a= t least have some form of snapshot in time. So, I can deploy it to our loca= l Maven repository under different group ID, but then I still have the unce= rtainty 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&q= uot; 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 relea= se is coming soon. There's also the awkward-ness of having a custom-bui= lt Groovy not-quite-2.4 but not-quite-2.5 version out and about. However, t= he 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 be= ta branch and validate.
>
> Jason
>
> -----Original Message-----
> From: Russel Winder [mailto:russel@winder.org.uk]
> Sent: Friday, January 15, 2016 2:29 PM
> To: users= @groovy.apache.org
> 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<= br> >> Groovy 2.5 beta milestoon soon?
> Probably not. I compile and install from source. Takes about 22 mins o= n my workstation (which is 9 years old so I expect modern kit to do better)= .
>
> --
> Russel.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
> Dr Russel Winder=C2=A0 =C2=A0 =C2=A0 t: +44 20 7585 2200= =C2=A0 =C2=A0voip: sip:russel.winder@ekiga.net
> 41 Buckmaster Road=C2=A0 =C2=A0 m: +44 7770 465 077=C2=A0 = =C2=A0xmpp: russe= l@winder.org.uk
> London SW11 1EN, UK=C2=A0 =C2=A0w: www.russel.org.uk=C2=A0 skype: r= ussel_winder
>
>
> ----------------------------------------------------------------------=
> This email message and any attachments are for the sole use of the int= ended recipient(s). Any unauthorized review, use, disclosure or distributio= n 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 an= y attachments.



--e89a8ffbabdb6f59d60529676de5--