Donát Csikós

This is the same problem that was described in #1238. In this case, the `org.graalvm.buildtools.native` contributes the classes directory to the Eclipse classpath. Currently we can only work around the...

That's a missing feature. In Eclipse, to include files and directories outside of the project dir, linked resources must be defined on the project. This is possible, but requires significant...

FYI, we decided to change the API and require the exception reference a mandatory method argument: https://github.com/gradle/gradle/pull/31844/files#diff-95d67bc14752cba0de62be9a2d229267b91901f498163671ea354a39efad2334R78

Hi Ed! Sorry for the late reply, I was offline in the past few weeks. The Tooling API jar is indeed not published to maven central. That the jar we...

The `org.jetbrains.kotlin.jvm` plugin contributes the build directories to the `testCompileClasspath`. Buildship puts both the production and the test dependencies to the same classpath, that's why you see it. There are...

Hi @kuzniarz I've rebased https://github.com/eclipse/buildship/tree/workspace-composites and https://github.com/eclipse/buildship/tree/kuzniarz-workspace-composites-rebased such that they are based on the latest master and all changes are squashed to the latest commits.

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4643

@reinsch82 I'm interested in your initial feedback.

Hi! Unfortunately I'm on sick leave at the moment. I'll get back to you with feedback next week.

@kuniss > As I understand, this would Buildship require to edit the settings.gradle file in the project, isn't it? You can define composites by adding the `--include-build ` arguments to...