Re: TeamCity back on track

2016-09-21 Thread Cédric Champeau
The elephant i see is that now that IBM (and Google is around the corner) > uses the OpenJDK, the OpenJDK implementation becomes the defacto standard > so recent 3rd party libraries tend to use OpenJDK specifics in their > implementation. Before, it was less an issue because there was multiple >

Re: TeamCity back on track

2016-09-20 Thread Jochen Theodorou
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

Re: TeamCity back on track

2016-09-20 Thread Remi Forax
- Mail original - > De: "Jochen Theodorou" <blackd...@gmx.org> > À: dev@groovy.apache.org > Envoyé: Dimanche 18 Septembre 2016 21:14:51 > Objet: Re: TeamCity back on track [...] > > so setAccessible is forbidden, but a subclass from a different module

Re: TeamCity back on track

2016-09-20 Thread Cédric Champeau
: *dev@groovy.apache.org >> *Envoyé: *Dimanche 18 Septembre 2016 14:39:30 >> *Objet: *Re: TeamCity back on track >> >> I can confirm this is a new error. Gradle 3.0 works with b119, but >> not b136. And from what I can see, this is *not* going to be t

Re: TeamCity back on track

2016-09-18 Thread Guillaume Laforge
with the jdk-9 build >> https://jdk9.java.net/download/ >> because this version doesn't integrate the change that enable 'stronger' >> encapsulation. >> >> Rémi >> >> - Mail original - >> > De: "Jochen Theodorou" <blackd...

Re: TeamCity back on track

2016-09-18 Thread Guillaume Laforge
se this version doesn't integrate the change that enable 'stronger' > encapsulation. > > Rémi > > - Mail original - > > De: "Jochen Theodorou" <blackd...@gmx.org> > > À: dev@groovy.apache.org > > Envoyé: Dimanche 18 Septembre 2016 19:09:13

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
rProcess.getEnv(WrapperProcess.java:110) > Is this "feature/bug" going to be fixed? Is there any way to disable that > behavior? > 2016-09-18 15:03 GMT+02:00 Remi Forax < fo...@univ-mlv.fr > : >>> De: "Cédric Champeau" < cedric.champ...@gmail.c

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
> De: "Cédric Champeau" <cedric.champ...@gmail.com> > À: dev@groovy.apache.org > Envoyé: Dimanche 18 Septembre 2016 14:39:30 > Objet: Re: TeamCity back on track > I can confirm this is a new error. Gradle 3.0 works with b119, but not b136. > And > fro

Re: TeamCity back on track

2016-09-18 Thread Cédric Champeau
e application classloader is now something that loads modules, so it's > not a subclass of URLClassLoader anymore. > > Rémi > > - Mail original - > > De: "Jochen Theodorou" <blackd...@gmx.org> > > À: dev@groovy.apache.org > > Envoyé:

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
...@gmx.org> > À: dev@groovy.apache.org > Envoyé: Dimanche 18 Septembre 2016 12:31:56 > Objet: Re: TeamCity back on track > On 18.09.2016 10:47, Cédric Champeau wrote: >> I just installed Jigsaw b136. Let me know if it helps. > > looks like gradle has a problem with this one as well > > bye Jochen

Re: TeamCity back on track

2016-09-18 Thread Jochen Theodorou
On 18.09.2016 10:47, Cédric Champeau wrote: I just installed Jigsaw b136. Let me know if it helps. looks like gradle has a problem with this one as well bye Jochen

Re: TeamCity back on track

2016-09-18 Thread Jochen Theodorou
On 18.09.2016 06:59, John Wagenleitner wrote: [...] Thanks Guillaume and Jochen. It's good to see green again. :-) now only the JDK9 builds are failing. At least for one of them I know it is because the version of jdk9 is too old. The JDK9 snapshot is failing with this: [22:28:52][Step