Mailing-List: contact users-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@groovy.apache.org
Subject: Re: Testing the Java 8 / Parrot parser online!
To: users@groovy.apache.org
References: <CAJ2HCd-=mEXW9ycyz9h0UrP9-vROz33Fz1VsY+KcHhLEv=d3Ug@mail.gmail.com>
 <1490424776.8008.7.camel@winder.org.uk>
From: Jochen Theodorou <blackdrag@gmx.org>
Message-ID: <58D629B1.6040504@gmx.org>
Date: Sat, 25 Mar 2017 09:26:25 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <1490424776.8008.7.camel@winder.org.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Sat, 25 Mar 2017 08:26:35 -0000

On 25.03.2017 07:52, Russel Winder wrote:
> On Fri, 2017-03-24 at 21:36 +0100, Guillaume Laforge wrote:
>> […]
>>
>> It's built with Java 8, and runs on the upcoming version of Google
>> App
>> Engine's Java runtime running on an OpenJDK 8. It's using the "indy"
>> jar,
>> thus with the invoke dynamic support automatically.
>> […]
>
> What is the exact difference between the indy artefacts and the non-
> indy artefacts?
>
> Why are we still making two complete sets of artefacts int eh Groovy
> build, surely now we should have just one.

I cannot suggest to users to use indy with a normal JDK7, so the minimum 
requirement for it is JDK8. And we are not there yet.

bye Jochen