Problems building java17 projects with Buildship 3.1.8 and Eclipse 202312 about buildship

[gundoghusse]

After more trial and horror, this seems to be related to "toolchain" issues (not finding the installed JDKs), but with really confusing error messages, I'm closing this issue

[MarioKusek]

I don't know if this is relevant to this problem but I had similar one.

In Problems View I had error regarding some library that could not be found. Gradle refresh did not help. But when you go to Project -> Properties -> Gradle there are set some program arguments like in picture here:

When I delete program arguments and refresh gradle project error disappears.

I hope this helps.

[oleosterhagen]

@gundoghusse I can reproduce your error when running Gradle 7.3 with Java 21. This is not supported, see Compatibility Matrix.

I think there are three possible solutions:

1. Switch the project to Gradle 8.5, e.g. Project > Properties: Override workspace settings > Specific Gradle version
2. Edit your eclipse.ini and start Eclipse with Java 17 (instead of Java 21)
3. Add this property to the gradle.properties in your project root: org.gradle.java.home=<path to Java 17> (see Gradle Properties)

[gundoghusse]

I don't know if this is relevant to this problem but I had similar one.

In Problems View I had error regarding some library that could not be found. Gradle refresh did not help. But when you go to Project -> Properties -> Gradle there are set some program arguments like in picture here:

When I delete program arguments and refresh gradle project error disappears.

I hope this helps.

Hi, unfortunately I didn't have any arguments so that did not help

[gundoghusse]

@gundoghusse I can reproduce your error when running Gradle 7.3 with Java 21. This is not supported, see Compatibility Matrix.

I think there are three possible solutions:

1. Switch the project to Gradle 8.5, e.g. Project > Properties: Override workspace settings > Specific Gradle version
2. Edit your eclipse.ini and start Eclipse with Java 17 (instead of Java 21)
3. Add this property to the gradle.properties in your project root: org.gradle.java.home=<path to Java 17> (see Gradle Properties)

Thanks for the reply, but I'm not sure that it helps.

Regarding step 1 above: We're unable to upgrade existing user/customer branches to gradle 8.5, and our developers need to be able to work on both the main branch (j21, gradle 8.5) and old branches (j21, gradle 7.3) in parallel . Does this mean that our users will have to have two separate eclipse installs as we are unable to upgrade the gradle version for old branches? We've never had to resort to that for any previous versions. Maybe I'm doing something wrong, but I run into a wall no matter what I do as soon as I want to build both branches with the same eclipse.

For step 2, I already have java 17 in eclipse.ini, which works for the j21-branches since they specify the JVM in the project settings.

For step 3, I suppose that's the same problem as for step 1, we cannot do a blanket upgrade of all branches.