ExE Boss

Turns out this got fixed in version 2.0.0.2

This still occurs when building a Gradle project that uses older versions of Gradle (eg. 3.5 or earlier).

Unfortunately, the project I’m experiencing this with depends on an old plugin that requires Gradle 3 or older and trying to build it on Gradle 4 causes the plugin to...

That’s what I tried, but then the plugin tries to invoke the Tooling API from Gradle 3, which is unable to interface with Java 9 that NetBeans runs on.

Knowing a real world example that this occurs in might potentially help you with solving this: - [NOVA-Team/NOVA-Core](https://github.com/NOVA-Team/NOVA-Core) - https://github.com/NOVA-Team/NOVA-Core/pull/314#issuecomment-374213503

I have `netbeans_jdkhome` set to point to JDK 9.0.4 if that helps. Here’s the full stack trace with “Prefer wrapper” checked: ``` Requested project: [redacted]\NOVA-Core Stack trace: org.gradle.tooling.GradleConnectionException: Could not...

Here’s my entire [`.nb-gradle-properties`](https://github.com/kelemen/netbeans-gradle-project/files/1845256/nb-gradle-properties.txt) file. Anyway, the `` is set to `1.8`: ```xml j2se 1.8 ``` Also, if I comment out the following from `settings.gradle`: ``` include "minecraft:1.8" include "minecraft:1.7"...

Or someone could fork it, convert it entirely to a WebExtension and publish it to AMO, à la [Tab Center Redux](https://addons.mozilla.org/firefox/addon/tab-center-redux/). Of course, the fork would also reqire merging of...

Also, it avoids unnecessary boxing.

I have already tested it with [Chrome Store Foxified](https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/) and it mostly worked. The main issue is that the custom CSS that is injected to add code coverage information is...