Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
MIME-Version: 1.0
Reply-To: paulk@asert.com.au
In-Reply-To: <9FF36391-6F7C-4D69-BB5C-5E515429E05B@selskabet.org>
References: <5880C018.3070204@gmx.org> <CAMbkE7TzfPPO8cRxzWvWcyv9SqVMumD_pG9OXqS+Z=LdysgD4w@mail.gmail.com>
 <f99ed6bd-ab85-333d-210c-4ce3c50e2abf@gmx.org> <CAMbkE7RQ-KR-1xdRTkTmcZ2pcvskLcnREENj-JQ1WFJXhz3pEQ@mail.gmail.com>
 <5882505D.1090304@gmx.org> <CAMbkE7R9kCc0dMSZXSxk3Pkzmc72d9ai1cNfSjur+yqLEXDESA@mail.gmail.com>
 <CADQzvmkrpOMDNrte4jfb8W-ajd6Fz=LiU5UBKVZeP167M9+EyQ@mail.gmail.com>
 <CAO_wNofgY4VNK3rdkH_GvTzV16BcVvy3oFy68qOGs-J+_N=98Q@mail.gmail.com>
 <cdf04552-c6f6-385e-d9ef-1d780279b16e@gmx.org> <CAO_wNodBKRtOqbzwYTTtGZLnbnH-p1x0d6UrYdrn_mHtc6LEdg@mail.gmail.com>
 <CADQzvmk4Oo9rQA6E1TREekTPSzSOiAQeP=Urz4QG4ziGp5b4gw@mail.gmail.com>
 <0ab19c9a-4a03-5786-8f8a-fb7f5d0e4a68@gmx.org> <9FF36391-6F7C-4D69-BB5C-5E515429E05B@selskabet.org>
From: Paul King <paulk@asert.com.au>
Date: Wed, 25 Jan 2017 06:22:33 +1000
Message-ID: <CAMbkE7RaCHn_5Y+bj5pUe3BMJipdqXHFTeZSpwzPTqXCo7EHLQ@mail.gmail.com>
Subject: Re: release process
To: dev@groovy.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 24 Jan 2017 20:22:40 -0000

I plan to experiment with creating an "uber" jar (maybe using a
different name) for 2.5 that would have the parrot parser. It would be
like the indy jars for now, requiring a move into the correct
directory to enable. But it isn't high up on my priority list just
yet.

Cheers, Paul.


On Wed, Jan 25, 2017 at 5:49 AM, Jesper Steen M=C3=B8ller
<jesper@selskabet.org> wrote:
> But - I recognise that the Antlr4 parser AST building looks really neat i=
n Java 8, but easthetics aside, wouldn=E2=80=99t it we a relatively easy ta=
sk to port back to Java 7?
>
> -Jesper
>
>
>> On 24 Jan 2017, at 16.59, Jochen Theodorou <blackdrag@gmx.org> wrote:
>>
>>
>>
>> On 24.01.2017 15:51, C=C3=A9dric Champeau wrote:
>>> The main problem is parrot is that it requires Java 8, and 2.5 is
>>> planned to support 1.7. And bundling such a core thing as an
>>> experimental, optional module is a no-go for me (imagine the bug
>>> reports...). We could have a 2.9 release (or something similar) with
>>> Parrot sooner, though.
>>>
>>> (as a side note, any release of Groovy that would require Java 8 would
>>> be a no-go for Gradle in short term, be it 2.x or 3.x)
>>
>> you misunderstand one essential part here. The parrot module would requi=
re java8, building Groovy would require Java8, executing Groovy would not r=
equire Java8 as long as parrot is not used. We have often parts of Groovy t=
hat require a higher version than the minimum one. At a time we required ja=
va5, but had a module for java6. Same for java7. Had we go with some propos=
als we would also have a java8 part while still requiring java7 as minimal =
version for Groovy.
>>
>> bye Jochen
>