Mailing-List: contact users-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@groovy.apache.org
Subject: Re: Groovy indy build
To: users@groovy.apache.org
References: <570EBAF3.5070702@teiemt.gr> <570E2F3E.3090402@gmx.org>
From: sterg <sterg@teiemt.gr>
Message-ID: <570ECA5D.5020303@teiemt.gr>
Date: Thu, 14 Apr 2016 01:38:21 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <570E2F3E.3090402@gmx.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


Thanks Jochen!

therefore, I think to have only the groovy-all-2.5.0-SNAPSHOT.jar at the 
classpath
is the best option, since it compiles also indy code,
and it can be a little more fast, since by itself it is consisted
of statically compiled classes only


Stergios


On 04/13/2016 02:36 PM, Jochen Theodorou wrote:
> On 13.04.2016 23:32, sterg wrote:
>> Hi all,
>>
>> I built Groovy from the sources on github in order to have the latest
>> built in GroovyLab.
>>
>> However, what the difference on the groovy-all-2.5.0-SNAPSHOT.jar
>> and the groovy-all-2.5.0-SNAPSHOT-indy.jar?
>
> the difference is that all the groovy classes are build with indy in 
> the -indy version, otherwise not.
>
> bye Jochen