TestNG build failing with JDK9 Jigsaw due to Gradle
cedric.champeau at gmail.com
Mon Nov 2 08:56:39 UTC 2015
BTW, Groovy itself is not compatible with Jigsaw, so my guess would be that
even if Gradle fixed this, you would have different errors because Gradle
uses Groovy. What is possible today is to run Gradle on Java 9 non jigsaw,
and compile using Java 9 Jigsaw.
Jochen sent an email on jigsaw-dev a few weeks ago ("Groovy with Jigsaw")
but as far as I understand, there's no clear understanding of the
problem/solutions so far.
2015-11-02 9:51 GMT+01:00 Rory O'Donnell <rory.odonnell at oracle.com>:
> I can't find a bug in Gradle's JIRA on this issue, Mani do you want to log
> an issue there ?
> On 31/10/2015 13:56, Alan Bateman wrote:
>> On 31/10/2015 12:50, Mani Sarkar wrote:
>>> Hi Rory,
>>> Do you know of a version of Gradle or a EA version which is JDK 9 Jigsaw
>>> compatible, we get these failures when building:
>>> Caused by: java.lang.IllegalAccessException: class
>> org.gradle.internal.reflect.DirectInstantiator cannot access class
>> com.sun.tools.javac.api.JavacTool (in module jdk.compiler) because module
>> jdk.compiler does not export package com.sun.tools.javac.api to <unnamed
>> module @b7f23d9>
>> ... 86 more
>> We should at least check if there is a bug in the Gradle JIRA for this.
>> It can be worked around by configuring the compileJava options to fork
>> javac but you might not want to do that.
>> The other issue with Gradle that we know about is the ClassCastException
>> when attempting to run tests, this is tracked here:
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland
More information about the jigsaw-dev