Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
Subject: Re: TeamCity back on track
To: dev@groovy.apache.org
References: <CAJ2HCd8Q+xHchR0RdKS3TPGgG8rJdXO5ew1zGRzoxr_nC_ZDWw@mail.gmail.com>
 <CAHPL-JnrioQ_q5OY0CtKmz_kj9NCGB3cMgVWi+KCTrYh3VjdnA@mail.gmail.com>
 <57DE46EA.2030704@gmx.org>
 <CADQzvmkvL8ytnsi3JJ-BsdM8pAv-PLmzSgrSGVxH+dSEGveg3Q@mail.gmail.com>
 <57DE6D1C.7040404@gmx.org>
 <334885618.2708801.1474197075494.JavaMail.zimbra@u-pem.fr>
 <CADQzvmn_NqB843=TVJFvZww7KDcEgxG2Xsr5dDHWkLtq_ZMXEg@mail.gmail.com>
 <CADQzvmkuqvdaR+CsvpXotjcT0ABEVg5TuM+yL6BJP+PgTyV+Yw@mail.gmail.com>
 <1784816423.2715948.1474203821312.JavaMail.zimbra@u-pem.fr>
 <57DEE7AB.8040800@gmx.org>
 <CADQzvm=obZBJX1nW0D9qi9m=gDi7GVLua_VA6vVPhYQ+3-MXCw@mail.gmail.com>
From: Jochen Theodorou <blackdrag@gmx.org>
Message-ID: <57E21BEA.2060804@gmx.org>
Date: Wed, 21 Sep 2016 07:34:34 +0200
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: <CADQzvm=obZBJX1nW0D9qi9m=gDi7GVLua_VA6vVPhYQ+3-MXCw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Wed, 21 Sep 2016 05:41:12 -0000

On 21.09.2016 00:20, Cédric Champeau wrote:
> I'm not able to answer the question why Gradle modifies the environment
> (I'm sure it does for good reasons), but we need to make it work on
> different platforms without having to publish a specific version for JDK
> 9. It's really unfortunate such a "feature" landed after the feature
> freeze. Our commitment that Gradle 3 runs on JDK 9 isn't true anymore,
> and it's hard to fix. Especially, the second exception you are seeing
> comes from a 3rd party library. I'm pretty sure we will face tons of
> those issues, especially in an environment where plugins are legion.

a workaround would be to use "--add-exports-private 
java.base/java.lang=ALL-UNNAMED" That should make the build work 
again... but of course it does not really solve the problem. And I 
actually do not think that switches like that are good for gradle, if 
that means I will run later my own programs with those switches enabled 
only from the build... because in the deployed state I will not have 
them set and then things break apart.

bye Jochen