IntelliJ IDEA tells me "Error:java: Compilation failed: internal java compiler error idea"

Question

When I compile a Java project using IntelliJ IDEA, it gives me the following output (and error):

Information:Eclipse compiler 4.6.2 was used to compile java sources
Information:Module "sinoWeb" was fully rebuilt due to project configuration/dependencies changes
Information:2017/3/23 11:44 - Compilation completed with 1 error and 0 warnings in 5m 32s 949ms
Error:java: Compilation failed: internal java compiler error

I'm quite confused confused by this! Below are my settings:

enter image description

enter image description here

Then try to provide a [mcve]. Not sure if we can help otherwise. Or write a bug report to JetBrains. — GhostCat, Mar 23 '17 at 04:37
In fact, my javaWeb project has some faults in other places. Maybe in other words, it's not a complete javaWeb project, so I have to use eclipse compiler instead of javac to ignore some errors. — ieatczp, Mar 23 '17 at 06:40

score 167 · Answer 1 · answered Oct 31 '18 at 10:58

167

On Intellij IDEA Ctrl + Alt + S to open settings.
Build, Execution, Deployment -> Compiler -> Java Compiler
choose your java version from Project bytecode version
Uncheck Use compiler from module target JDK when possible
click apply and ok.

answered Oct 31 '18 at 10:58

Musab Bozkurt

1,771
1
6
5

17

Ok, so I did the rain dance and it worked, but why? – Marthinus Engelbrecht Apr 25 '20 at 14:02
2

I also set the "Target bytecode version" for my module and then it worked without issues. – Sathesh Jan 04 '21 at 22:14
1

@MarthinusEngelbrecht The bytecode differs according to the JVM version, and hence when you set all to be the same or in this case to be null, it picks from the project settings. https://www.baeldung.com/java-lang-unsupportedclassversion – gagneet Mar 03 '21 at 03:13
works like charm. – 9f241e21 May 22 '22 at 02:11
for me, on a mac, it was cmd + , to open settings. Or you can click on "IntelliJ IDEA" and then Preferences – sFishman Jan 12 '23 at 11:02

score 86 · Answer 2 · answered Feb 02 '18 at 15:17

86

I solved this issue by increasing the default value(700) of Build process heap size on IntelliJ's compiler settings.

answered Feb 02 '18 at 15:17

sezerug

1,136
9
10

3

This is what solved it for me! Would sit there for 25 minutes and fail otherwise. – nevster Oct 25 '21 at 06:47

score 51 · Answer 3 · answered Jul 24 '17 at 07:41

51

I changed my compiler to Eclipse and run my project. Afterwards changed back to Javac and problem solved. I don't know exact problem but it can help who is looking for solution.

answered Jul 24 '17 at 07:41

omerhakanbilici

874
1
18
26

8

This worked for me also. No idea why, but I'll take it! – Wpigott Jun 28 '20 at 18:25
1

Unbelievable. This worked for me and I completely lose my mind. – Roeniss Aug 12 '22 at 19:19

score 29 · Answer 4 · answered Jul 26 '19 at 07:16

29

In my case, using Java 11, I had:

 public List<String> foo() {
   ...
   return response.readEntity(new GenericType<List<String>>() {});

and Intellij suggested I should use <> instead of GenericType<List<String>>, as such:

 public List<String> foo() {
   ...
   return response.readEntity(new GenericType<>() {});

I did that in four functions and the project stopped compiling with an internal compiler error, reverted and it compiled again. Looks like a bug with type inference.

answered Jul 26 '19 at 07:16

Tony BenBrahim

7,040
2
36
49

2

Same pattern here, JDK 11 (11.0.3 and tested 11.0.5), compiled fine in maven, but `Error:java: Compilation failed: internal java compiler error` in IntelliJ 2019.2.2; Crash was `java.lang.NullPointerException` on `jdk.compiler/com.sun.tools.javac.comp.Flow$FlowAnalyzer.visitApply(Flow.java:1235)`. Added the explicit type for the generic and problem went away. Thanks for the posting your case it helped me figure out mine :) – GaspardP Dec 01 '19 at 19:43
Thanks. JDK 11 here too. Same problem. – FFEVER Oct 05 '20 at 06:50
that was EXACTLY the same problem I was having, thanks for posting tony – Martin Charlesworth Jan 11 '21 at 17:24

score 23 · Answer 5 · answered Sep 16 '19 at 10:27

23

In my case it was because of lombok library with intellij 2019.2 & java11.

According to this IDEA bug after workaround idea works again:

Disable all building from intelliJ and dedicate the build to Maven.

answered Sep 16 '19 at 10:27

Filomat

753
1
11
16

Thank you! This worked and, IMO, is the best solution for Maven-based projects because any manual changes to compiler settings etc. will get reset after your Maven-based project is re-imported. – ehsanullahjan Jul 03 '20 at 19:22
This worked but still it does not stop on breakpoints in debugging and never terminate the debugged process. – lrkwz Nov 18 '20 at 13:09
This was also happening on a project without Lombok usage, Java 8, idea 2020.3. But with the Lombok plugin installed. Doing what suggested fixed it also for me, not sure if it's related or not.. – Shahar Levy Feb 24 '21 at 08:32

score 21 · Answer 6 · answered Aug 08 '20 at 03:04

In JIdea 2020.1.2 and above,

This is may be the language-level set in Project Structure is not compatible with the target byte-code version.

You have to change the target bytecode version .

Go to Settings [ Ctrl+Alt+S ]
Select Java Compiler
Select module in the table
Change the byte-code version to map what you selected in the previous step for language-level

NOTE : How to check the language-level

Go to Project Structure [ Ctrl+Alt+Shift+S ]
Select Modules sub section
Select each module
Under sources-section, check Language Level

Worked like a charm, thanks – Raj Rajeshwar Singh Rathore Jan 13 '22 at 15:19 — Raj Rajeshwar Singh Rathore, Jan 13 '22 at 15:19

score 20 · Answer 7 · answered Apr 17 '20 at 10:40

20

For me the module's target bytecode version was set to 5. I changed it to 8 and the error is gone:

answered Apr 17 '20 at 10:40

velocity

1,630
21
24

score 8 · Answer 8 · edited Apr 19 '21 at 17:38

8

I met the same problem

I solved it by changing the Target bytecode error from 1.5 to 8

edited Apr 19 '21 at 17:38

Brad Mace

27,194
17
102
148

answered Jan 09 '21 at 09:49

kl w

81
1
2

score 6 · Answer 9 · edited Apr 17 '19 at 14:39

6

You have to disabled the Javac Options: Use compiler from module target JDK when possible.

edited Apr 17 '19 at 14:39

Maximilian Ast

3,369
12
36
47

answered Apr 17 '19 at 14:04

Duc Hiep Hoang

71
1
3

score 6 · Answer 10 · answered May 19 '20 at 09:38

6

In my case, it was response type in restTemplate:

ResponseEntity<Map<String, Integer>> response = restTemplate.exchange(
        eurl,
        HttpMethod.POST,
        requestEntity,
        new ParameterizedTypeReference<>() { <---- this causes error
        }
);

Should be like this:

ParameterizedTypeReference<Map<String, Integer>> responseType = new ParameterizedTypeReference<>() {};

ResponseEntity<Map<String, Integer>> response = restTemplate.exchange(
        url,
        HttpMethod.POST,
        requestEntity,
        responseType
);

answered May 19 '20 at 09:38

dev_in_progress

2,484
2
21
32

I just ran into the same problem and I'm really glad I stumbled across this answer, and I'm scratching my head why this is. This code here works, too: restTemplate.exchange(url, HttpMethod.GET, request, new ParameterizedTypeReference>() {}); It seems that the Java compiler has issues inferring the correct type if you use <>. But still IntelliJ suggests to replace the explicit version with <>. And the error message from the compiler is completely worthless, too. Doesn't even mention the file that causes the issue! – Christoph Sep 14 '20 at 10:22

score 5 · Answer 11 · answered May 03 '22 at 18:00

It May is not be relevant to this case, but:

I got this error when I change the Explicit type argument List of:

new ParameterizedTypeReference<List<SomeDtoObject>>()

to <> :

new ParameterizedTypeReference<>()

in restTemplate call after Intellij gave the warning to use <> instead.

It got fixed when I undo my changes back into the Explicit type argument.

score 2 · Answer 12 · answered Jul 27 '18 at 07:52

2

Changing the Language Level in the Project Settings (Ctrl + Alt + Shift + S) to Java 8 solved the problem for me

answered Jul 27 '18 at 07:52

Chris K.

1,060
8
10

score 1 · Answer 13 · answered Jun 15 '20 at 21:30

1

I had the same problem. I fixed changing my settings. Target bytecode version for equals Project bytecode version.

answered Jun 15 '20 at 21:30

Thiago de Melo Fontana

347
2
4
15

score 1 · Answer 14 · answered Jun 17 '20 at 11:26

1

What worked for me is to update the Open JDK version

answered Jun 17 '20 at 11:26

NobuhleM

11
2

score 1 · Answer 15 · answered Apr 03 '21 at 23:17

I got the same error with Community edition 2020.3 on Windows 10 with an older version of the JDK (openjdk version "11" 2018-09-25).

Updating the JDK to javac 11.0.10 fixed the issue.

Here's the stack trace that showed up with the error when using openjdk version "11" 2018-09-25:

java: compiler message file broken: key=compiler.misc.msg.bug arguments=11, {1}, {2}, {3}, {4}, {5}, {6}, {7}
java: java.lang.AssertionError
java:   at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155)
java:   at jdk.compiler/com.sun.tools.javac.util.Assert.check(Assert.java:46)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$2$1.setOverloadKind(DeferredAttr.java:172)
java:   at jdk.compiler/com.sun.tools.javac.comp.ArgumentAttr.visitReference(ArgumentAttr.java:283)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMemberReference.accept(JCTree.java:2190)
java:   at jdk.compiler/com.sun.tools.javac.comp.ArgumentAttr.attribArg(ArgumentAttr.java:197)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribTree(Attr.java:653)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribArgs(Attr.java:751)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitApply(Attr.java:1997)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1634)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribTree(Attr.java:655)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3573)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCFieldAccess.accept(JCTree.java:2110)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2006)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitReturn(Attr.java:1866)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCReturn.accept(JCTree.java:1546)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribStat(Attr.java:724)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribStats(Attr.java:743)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:1294)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1020)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr.attribSpeculative(DeferredAttr.java:498)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr.attribSpeculative(DeferredAttr.java:481)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr.attribSpeculativeLambda(DeferredAttr.java:456)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredAttrNode$StructuralStuckChecker.canLambdaBodyCompleteNormally(DeferredAttr.java:900)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredAttrNode$StructuralStuckChecker.visitLambda(DeferredAttr.java:878)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCLambda.accept(JCTree.java:1807)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredAttrNode$StructuralStuckChecker.complete(DeferredAttr.java:832)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredType.check(DeferredAttr.java:335)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredAttrNode.process(DeferredAttr.java:779)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredAttrContext.complete(DeferredAttr.java:626)
java:   at jdk.compiler/com.sun.tools.javac.comp.Infer.instantiateMethod(Infer.java:214)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.rawInstantiate(Resolve.java:605)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.selectBest(Resolve.java:1563)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.findMethodInScope(Resolve.java:1733)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.findMethod(Resolve.java:1802)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.findMethod(Resolve.java:1776)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve$10.doLookup(Resolve.java:2654)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve$BasicLookupHelper.lookup(Resolve.java:3293)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.lookupMethod(Resolve.java:3543)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.resolveQualifiedMethod(Resolve.java:2651)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.resolveQualifiedMethod(Resolve.java:2645)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.selectSym(Attr.java:3721)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3601)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitLambda(Attr.java:2598)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$4.complete(DeferredAttr.java:374)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredType.check(DeferredAttr.java:321)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve$MethodResultInfo.check(Resolve.java:1060)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve$4.checkArg(Resolve.java:887)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve$AbstractMethodCheck.argumentsAcceptable(Resolve.java:775)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve$4.argumentsAcceptable(Resolve.java:896)
java:   at jdk.compiler/com.sun.tools.javac.comp.Infer.instantiateMethod(Infer.java:181)
java:   at jdk.compiler/com.sun.tools.javac.comp.Resolve.checkMethod(Resolve.java:644)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.checkMethod(Attr.java:4120)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.checkIdInternal(Attr.java:3913)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.checkMethodIdInternal(Attr.java:3814)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.checkId(Attr.java:3803)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3696)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitLambda(Attr.java:2595)
java:   at jdk.compiler/com.sun.tools.javac.comp.DeferredAttr$DeferredAttrNode.process(DeferredAttr.java:811)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitIdent(Attr.java:3553)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCIdent.accept(JCTree.java:2243)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribExpr(Attr.java:702)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitExec(Attr.java:1773)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCExpressionStatement.accept(JCTree.java:1452)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.visitMethodDef(Attr.java:1098)
java:   at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:866)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribClassBody(Attr.java:4683)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribClass(Attr.java:4574)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribClass(Attr.java:4523)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attribClass(Attr.java:4503)
java:   at jdk.compiler/com.sun.tools.javac.comp.Attr.attrib(Attr.java:4448)
java:   at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.attribute(JavaCompiler.java:1341)
java:   at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:973)
java:   at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104)
java:   at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147)
java:   at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100)
java:   at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94)
java:   at org.jetbrains.jps.javac.JavacMain.compile(JavacMain.java:231)
java:   at org.jetbrains.jps.incremental.java.JavaBuilder.compileJava(JavaBuilder.java:501)
java:   at org.jetbrains.jps.incremental.java.JavaBuilder.compile(JavaBuilder.java:353)
java:   at org.jetbrains.jps.incremental.java.JavaBuilder.doBuild(JavaBuilder.java:277)
java:   at org.jetbrains.jps.incremental.java.JavaBuilder.build(JavaBuilder.java:231)
java:   at org.jetbrains.jps.incremental.IncProjectBuilder.runModuleLevelBuilders(IncProjectBuilder.java:1441)
java:   at org.jetbrains.jps.incremental.IncProjectBuilder.runBuildersForChunk(IncProjectBuilder.java:1100)
java:   at org.jetbrains.jps.incremental.IncProjectBuilder.buildTargetsChunk(IncProjectBuilder.java:1224)
java:   at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunkIfAffected(IncProjectBuilder.java:1066)
java:   at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunks(IncProjectBuilder.java:832)
java:   at org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:419)
java:   at org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:183)
java:   at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:132)
java:   at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:302)
java:   at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:132)
java:   at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler.lambda$channelRead0$0(BuildMain.java:219)
java:   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
java:   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java:   at java.base/java.lang.Thread.run(Thread.java:834)
java: Compilation failed: internal java compiler error
java: Errors occurred while compiling module 'project'
javac 11 was used to compile java sources
Finished, saving caches...
Compilation failed: errors: 1; warnings: 100

score 1 · Answer 16 · answered Jul 06 '21 at 05:54

1

Setting -> Build -> Compiler -> Java Compiler The Target bytecode version of the module is wrong. I set it to 1.8, then it worked.

answered Jul 06 '21 at 05:54

rosa

87
1
3

score 1 · Answer 17 · answered Aug 25 '21 at 07:19

1

In my case Information:java: java.lang.OutOfMemoryError: GC overhead limit exceeded intellij.

increased compiler -> build process heap size.

Ref: https://intellij-support.jetbrains.com/hc/en-us/community/posts/360003315120-GC-overhead-limit-exceeded

answered Aug 25 '21 at 07:19

Sureshkumar Natarajan

428
1
5
14

score 1 · Answer 18 · answered Nov 27 '21 at 19:27

In my case I had to go to help > show logs in files which opens up the idea.log and build-log folders something like

/home/user/.cache/JetBrains/IntelliJIdea2021.2/log/build-log/ where I set the log level to DEBUG in the log4j.rootLogger=debug, file in build-log.properties

I then ran build again and saw

2021-11-27 19:59:39,808 [ 133595]  DEBUG - s.incremental.java.JavaBuilder - Compiling chunk [module] with options: "-g -deprecation -encoding UTF-8 -source 11 -target 11 -s /home/user/project/target/generated-test-sources/test-annotations", mode=in-process
2021-11-27 19:59:41,082 [ 134869]  DEBUG - s.incremental.java.JavaBuilder - java:ERROR:Compilation failed: internal java compiler error

which lead me to see that this might me related to junit test compilation failing. It turns out I had an older/mismatching of the vintage engine and the jupiter engine which are likely to have different java versions relating in the error above. Changing them to be the same ${version.junit} removed the error.

  <dependency>
            <groupId>org.junit.platform</groupId>
            <artifactId>junit-platform-launcher</artifactId>
            <version>1.6.2</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.junit.platform</groupId>
            <artifactId>junit-platform-commons</artifactId>
            <version>1.7.1</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter-engine</artifactId>
            <version>${version.junit}</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.junit.vintage</groupId>
            <artifactId>junit-vintage-engine</artifactId>
            <version>${version.junit}</version>
            <scope>test</scope>
        </dependency>

In short some of your dependency jars may have mismatching java versions.

Thank you for your solution, but in the latest version, the log configuration has changed. The latest log configuration file is `build-log-jul.properties`, so the configuration method of jul needs to be followed: ```properties # Configure the level of rootLogger .level=FINER ``` — kongwu, Jul 06 '22 at 11:55

score 1 · Answer 19 · answered Aug 10 '22 at 17:35

1

Was facing the same issue with Java 11. Solved by changing language level

File -> Project Structure -> Project

Change "Language Level" to SDK Default

answered Aug 10 '22 at 17:35

Harshvardhan Chittora

137
1
10

score 0 · Answer 20 · answered May 06 '21 at 10:25

0

Updated Java compiler to correct "Target bytecode version" which in my case is 8 :

answered May 06 '21 at 10:25

blue-sky

51,962
152
427
752

score 0 · Answer 21 · answered Jul 16 '21 at 03:41

0

one reason may be jdk version donot macth minimal version of your project.

answered Jul 16 '21 at 03:41

user13243683

1

Can you give a solution to resolve this problem? – Allen Jul 16 '21 at 08:52

score 0 · Answer 22 · answered Aug 10 '21 at 12:52

Be aware of JDK-8177068 issue, which leads to internal error like

java.lang.NullPointerException
        at jdk.compiler/com.sun.tools.javac.comp.Flow$FlowAnalyzer.visitApply(Flow.java:1233)
        at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1628)
        at jdk.compiler/com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:49)
        at jdk.compiler/com.sun.tools.javac.comp.Flow$BaseAnalyzer.scan(Flow.java:393)
        at jdk.compiler/com.sun.tools.javac.tree.TreeScanner.visitExec(TreeScanner.java:213)
        ...

It was fixed in JDK 11.0.12 and JDK 14 b14, so upgrade helped.

score 0 · Answer 23 · answered Aug 22 '22 at 10:57

I switched across to the cmd line mvn compile build and it showed a more meaningful error.

Fatal error compiling: error: invalid target release: 17 -> [Help 1]

Checking my JAVA_HOME it was set to 11. Once I adjust my project to use 11 as well I got past this and onto another error (which was solved separately).

score 0 · Answer 24 · answered Oct 08 '22 at 20:39

0

Otherwise you can remove .m2 folder. Try to reload project.

answered Oct 08 '22 at 20:39

Ali Can

1
1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Oct 13 '22 at 18:31

score 0 · Answer 25 · answered Dec 13 '22 at 06:08

In my case, I was using Spring Framework 6.0.0 and JDK 11 as the same time. This is not supported according to spring framework wiki. After I degraded the spring framework version to 5.3.24, it solved.

You can check your spring framework version in this way. spring framework version

score 0 · Answer 26 · answered Jul 13 '23 at 10:16

0

In my case, a mvn clean install recreated the generated-sources in target, it seems that this caused the issue.

answered Jul 13 '23 at 10:16

Andrei Morosan

41
5

score 0 · Answer 27 · answered Aug 23 '23 at 02:38

0

In my case, deleting the .idea folder and then reimporting the project again solves this problem. This problem happens to me when I run a unit test.

answered Aug 23 '23 at 02:38

paul

372
4
17

IntelliJ IDEA tells me "Error:java: Compilation failed: internal java compiler error idea"

27 Answers27

Linked