apache / apache/ignite

Spring Tools for Eclipse Java build error with Ignite3's ErrorCodeGroupProcessor

Open
#12,592 1 comment 0 reactions 0 assignees View on GitHub
ignite-3
Dominant language
Java
Stars
5.1k
Forks
1.9k
Avg merge
3d 2h
Merged PRs (30d)
46

Description

I'm using the latest Spring Tools for Eclipse 5.0 and I'm getting an exception in the Eclipse's Java Builder for my Maven project that includes the ignite3-jdbc:3.1.0 dependency.

When I look in the Eclipse logs, I see an exception (below) that looks like Eclipse is picking up Ignite3 library in the class path with ErrorCodeGroupProcessor class and there is an incompatibility with the JustJ OpenJDK version of Java 25. I also saw this same issue with a slightly older version Spring Tool Suite using JustJ OpenJDK 21 version.

Eclipse log:
```
java.lang.IllegalArgumentException
at jdk.compiler/com.sun.source.util.Trees.instance(Trees.java:84)
at org.apache.ignite.internal.error.code.processor.ErrorCodeGroupProcessor.init(ErrorCodeGroupProcessor.java:64)
at org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.discoverNextProcessor(IdeAnnotationProcessorManager.java:91)
at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.round(RoundDispatcher.java:120)
at org.eclipse.jdt.internal.compiler.apt.dispatch.BaseAnnotationProcessorManager.processAnnotations(BaseAnnotationProcessorManager.java:177)
at org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.processAnnotations(IdeAnnotationProcessorManager.java:132)
at org.eclipse.jdt.internal.compiler.Compiler.processAnnotations(Compiler.java:859)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:333)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:309)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:486)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.compile(BatchImageBuilder.java:253)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:377)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:118)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:312)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:224)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:1109)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:299)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:355)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:449)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:452)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:564)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:512)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:594)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:208)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:309)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
```

Contributor guide

Open the contributing guide

Research direction

Reproduce the Eclipse Java Builder failure with the ignite3-jdbc:3.1.0 Maven dependency in Spring Tools for Eclipse, using the logged stack trace as the starting point. Inspect org.apache.ignite.internal.error.code.processor.ErrorCodeGroupProcessor at line 64 and determine why Trees.instance fails; done means the project builds without this exception on the affected JustJ JDK versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.