Error:BUG! exception in phase 'class generation' in source unit '_BuildScript_' unsupported Target MODULE

Question

I'm trying to create a new Java 9 project using gradle but right after project creation I received error from gradle:

Error:BUG! exception in phase 'class generation' in source unit '_BuildScript_' unsupported Target MODULE

Java version: 9 (build 9+178)
Gradle version: 4.1-rc-2

According to this article those java/gradle versions should be compatible.
How can I solve this problem?

Any help highly appreciated.

Can you share the Gradle event logs for this failure as well or/and a minimal project that can be tried out to reproduce this please. — Naman, Aug 27 '17 at 03:07
what version of grade did you use? i used 4.1, still got the same error. — Narendran Solai Sridharan, Aug 29 '17 at 08:14
Something similar happened for me, here is how I fixed it https://stackoverflow.com/a/53509014/1195507 — rvazquezglez, May 14 '19 at 00:17
Had same error message. After too many hours - turned out to be @Deprecated annotation in front of an abstract class. — slaman, Jun 30 '21 at 02:37

score 23 · Accepted Answer · edited Sep 22 '17 at 13:41

23

I have solved it by downgrading Gradle JVM to 8. It is not perfect but keeps you going while jdk9 and gradle and intellij stabilises.

edited Sep 22 '17 at 13:41

answered Aug 30 '17 at 21:17

kamaz

score 7 · Answer 2 · answered Aug 29 '17 at 09:47

7

Setting the Gradle home to local Gradle distribution solved the issue in my case.

if we set to use default Gradle wrapper, IntelliJ downloads an earlier version of Gradle. I think it is the reason for failure.

answered Aug 29 '17 at 09:47

Any additional step to follow? In my case it isn't working with this configuration: jdk9+181, gradle 4.1, idea 2017.2.4, linux – oidualc Sep 17 '17 at 06:44
I did not have any issues. since gradle is a build tool, you could try to downgrade JVM of build tool to 1.8 and give a try. – Narendran Solai Sridharan Sep 17 '17 at 15:28
Yes, for the moment I'm doing this – oidualc Sep 17 '17 at 19:33
Didn't work for me too. Went back to JDK8 (with Gradle 4.1) which works fine. Will wait some days – dominic.e Sep 20 '17 at 11:56
If on macOS and Gradle has been installed with Homebrew, then `brew --prefix gradle` reveals the location of where `libexec/` can be found. For me, that is `/usr/local/opt/gradle`, so I set my project's Gradle home to `/usr/local/opt/gradle/libexec`. I'm sure Windows' alternative Chocolatey has a similar function to find the latest installation directory. – Erik Oct 12 '17 at 16:49

score 3 · Answer 3 · answered Oct 04 '17 at 17:03

3

Seems fixed in 2017.3

answered Oct 04 '17 at 17:03

Sormuras

score 3 · Answer 4 · answered Nov 12 '21 at 14:20

3

This issue seems to have been fixed in Groovy 2.4.12 and upgrading to at least that version resolved a similar problem in https://github.com/jenkinsci/JenkinsPipelineUnit/issues/292.

answered Nov 12 '21 at 14:20

dB.

4 Answers4