TestNG build failing with JDK9 Jigsaw due to Gradle

[Jochen Theodorou]

Hi,

Jochen here, not Rory, but Groovy maintainer ;) So for Groovy reporting 
on the mailing list is good, if you also want to discuss the bug a bit 
there. If you really only want to report it, then you can just write it 
in the bug tracker. Of course Gradle is Gradle and Groovy is Groovy

bye Jochen

On 02.11.2015 23:23, Mani Sarkar wrote:
> Hi Rory,
>
> TestNG has an alternative build system which we will try to use to build
> it using the Jigsaw binary.
>
> How do you report such bugs to Gradle / Groovy ? Is it simpler if you
> reported to them on their mailing list ? Let me know what works best,
> this is fairly important as other Gradle users might have similar issues.
>
> Cheers,
> Mani
>
> On Mon, Nov 2, 2015 at 8:51 AM, Rory O'Donnell <rory.odonnell at oracle.com
> <mailto:rory.odonnell at oracle.com>> wrote:
>
>     I can't find a bug in Gradle's JIRA on this issue, Mani do you want
>     to log an issue there ?
>
>     Rgds,Rory
>
>
>     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:
>
>             https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG-Jigsaw/5/console
>
>
>         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>
>              at
>         org.gradle.internal.reflect.DirectInstantiator.newInstance(DirectInstantiator.java:49)
>              ... 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:
>         https://issues.gradle.org/browse/GRADLE-3287
>
>         -Alan.
>
>
>     --
>     Rgds,Rory O'Donnell
>     Quality Engineering Manager
>     Oracle EMEA , Dublin, Ireland
>
>
>
>
> --
> @theNeomatrix369 <http://twitter.com/theNeomatrix369>*  | **Blog
> <http://neomatrix369.wordpress.com>**  | *LJC Associate & LJC Advocate
> (@adoptopenjdk & @adoptajsr programs)
> *Meet-a-Project - *MutabilityDetector
> <https://github.com/MutabilityDetector>*  | **Bitbucket
> <https://bitbucket.org/neomatrix369>* * | **Github
> <https://github.com/neomatrix369>** | **LinkedIn
> <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/
>
> */Don't chase success, rather aim for "Excellence", and success will
> come chasing after you!/*