Donát Csikós

The problem is indeed the JustJ. Right now the only workaround I was able to find is to use a standalone JDK for Eclipse.

Not really at the moment, however, we'll soon implement new APIs that might be useful for you. We're going enable clients to [hook into the project synchronization](https://github.com/eclipse/buildship/issues/326) and to [access...

I have (sort of a) workaround. I've implemented a [sample Buildship extension](https://github.com/donat/buildship-sample-encoding) that reads the encoding from the Java compile options and sets it the corresponding Eclipse workspace project. It's...

From @onmishkin ``` The just-released Eclipse 2022-06 (4.24) has some changes WRT project-level info about what character encoding is used for files in the project. See [this 4.24 New &...

Since this is a requirement now, the feature should be prioritized.

Buildship updates the compiler properties as follows: - Eclipse's compiler compliance level and source compatibility is updated to Gradle' `sourceCompatibility` - Eclipse's generated `.class` file compatibility is updated to Gradle's...

What happens if you install a proper Java 1.8 JDK in the `Installed JREs` section?

Can you please elaborate on the problem? What's the expected and actual behavior?

Can you please paste .classpath file content here from the maven project? I'm curious how the "grey" dependencies are defined. By default, the grey icon is used for dependencies that...

You are right, it's not particularly helpful. m2e pulls the same trick as Buildship: they both contribute a classpath container where the dependencies are listed.