Recent commit breaks gradle builds

2016-09-18 Thread John Wagenleitner
A recent commit [1] to ClassInfo changed a private field from a Class to a WeakReference (to address memory leaks). In testing a project with the latest snapshot as a dependency, the compileGroovy task fails [2] because that field is referenced in an internal Gradle class LeakyOnJava7GroovySystemL

Re: TeamCity back on track

2016-09-18 Thread Jochen Theodorou
On 18.09.2016 15:03, Remi Forax wrote: *De: *"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

Re: TeamCity back on track

2016-09-18 Thread Guillaume Laforge
Ok, thanks for confirming this. On Sun, Sep 18, 2016 at 8:18 PM, Remi Forax wrote: > > > -- > > *De: *"Guillaume Laforge" > *À: *dev@groovy.apache.org > *Envoyé: *Dimanche 18 Septembre 2016 20:11:20 > *Objet: *Re: TeamCity back on track > > But we'll face it at some

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
> De: "Guillaume Laforge" > À: dev@groovy.apache.org > Envoyé: Dimanche 18 Septembre 2016 20:11:20 > Objet: Re: TeamCity back on track > But we'll face it at some point when this change becomes integrated in the > version we can download from java.net , right? yes, note that there are still dis

Re: TeamCity back on track

2016-09-18 Thread Guillaume Laforge
But we'll face it at some point when this change becomes integrated in the version we can download from java.net, right? On Sun, Sep 18, 2016 at 7:56 PM, Remi Forax wrote: > Your code should work with the jdk-9 build > https://jdk9.java.net/download/ > because this version doesn't integrate t

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
Your code should work 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" > À: dev@groovy.apache.org > Envoyé: Dimanche 18 Septembre 2016 19:09:13

Re: TeamCity back on track

2016-09-18 Thread Jochen Theodorou
On 18.09.2016 15:03, Remi Forax wrote: [...] This one is a new bug/feature, it's part of what we have called 'stronger' (not strong) encapsulation i.e. most of the classes of java.* disallow setAccessible, before that only internal packages were disallowing setAccessible. For your specific bug,

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
The real question is why Gradle want to modify the environment of the current process given that ProcessBuilder::environment() exists. Rémi > De: "Remi Forax" > À: dev@groovy.apache.org > Envoyé: Dimanche 18 Septembre 2016 16:59:32 > Objet: Re: TeamCity back on track > It's a feature, > so y

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
It's a feature, so you can easily detect sofwares that try to do reflection using setAccessible, i.e. violates the VM access rules to, by example, get access to a security token, what is not known is which part of the JDK should allow this kind of reflection (think things like sun.misc.Unsafe.

Re: TeamCity back on track

2016-09-18 Thread Cédric Champeau
Thanks but I'm afraid it won't allow me to boot Gradle either. Even after trying `getDefinedPackages` instead, I only reach another error of this kind: Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make private final java.util.Map java.util.Collections$UnmodifiableMap.m acces

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
> De: "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 trivial to fix. Best I could

Re: TeamCity back on track

2016-09-18 Thread Cédric Champeau
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 trivial to fix. Best I could get now is: Caused by: java.lang.IllegalAccessException: class org.gradle.internal.reflect.JavaMethod cannot access a member of class java.la

Re: Latest documentation not showing up

2016-09-18 Thread Guillaume Laforge
Oh nice find! Thanks! On Sun, Sep 18, 2016 at 2:24 PM, Cédric Champeau wrote: > Fixed. The CI build that explodes the documentation was still looking for > "groovy-docs.zip" instead of "apache-groovy-docs.zip". > > > 2016-09-18 14:19 GMT+02:00 Guillaume Laforge : > >> Hi, >> >> Any idea why the

Re: Latest documentation not showing up

2016-09-18 Thread Cédric Champeau
Fixed. The CI build that explodes the documentation was still looking for "groovy-docs.zip" instead of "apache-groovy-docs.zip". 2016-09-18 14:19 GMT+02:00 Guillaume Laforge : > Hi, > > Any idea why the "latest" documentation online: > http://docs.groovy-lang.org/docs/next/html/documentation/ >

Latest documentation not showing up

2016-09-18 Thread Guillaume Laforge
Hi, Any idea why the "latest" documentation online: http://docs.groovy-lang.org/docs/next/html/documentation/ isn't showing up the latest bits of doc, for instance the @AutoImplement transformation is not displayed, although it's indeed in master. And when I generate it locally, it's indeed ther

Re: TeamCity back on track

2016-09-18 Thread Cédric Champeau
This seems to be a new error, I've never seen it before with Gradle 3.0+. It says: [Gradle failure report] Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected java.lang.Package[] java.lang.ClassLoader.getPackages() accessible: module java.base does not "exports priva

Re: TeamCity back on track

2016-09-18 Thread Remi Forax
Gradle thinks it can hack the classpath by seeing the application classloader as an URLClassLoader. The application classloader is now something that loads modules, so it's not a subclass of URLClassLoader anymore. Rémi - Mail original - > De: "Jochen Theodorou" > À: dev@groovy.apache.

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 Cédric Champeau
I just installed Jigsaw b136. Let me know if it helps. 2016-09-18 9:48 GMT+02:00 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

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 2/