Shi Chen

@donat I added a simple closure in `org.eclipse.buildship.core.test/build.gradle`: ``` tasks.getByName("crossVersionEclipseTest") { javaLauncher = javaToolchains.launcherFor { languageVersion = JavaLanguageVersion.of(17) } } ``` and running test via `gradlew crossVersionEclipsetest` in java 11...

@donat thanks! I'll rebase and try again.

hey @donat , thanks for reminding. I just rebased this branch and adopted the new properties. I did a test on my local machine with the following steps: 1. specify...

@donat I just pushed a new commit https://github.com/eclipse/buildship/pull/1161/commits/b3ebed60b964469e446af96af1d1d01be0cf9ef7 to enable `Can not import a simple project` and `Can import a simple project` tests, which will assert the import status with...

@donat sorry for replying late. I have pushed https://github.com/eclipse/buildship/pull/1161/commits/17ef0b7152fc345509ec109816c6144627588687 to address the comments and add tests to guard the scenarios we mentioned at https://github.com/eclipse/buildship/pull/1161#discussion_r911660408

@donat I just rebase this branch to the newest upstream/master and did crossversion tests in my local PC for all Java versions, feel free to trigger a new CI build....

IMO it makes sense overall, after the integration test, we can update the mentioned compatibility matrix and check version's combination before the actual synchronization. and I just wonder about our...

Thanks for the detailed clarification, I got it. In this way, should the new status (inferred from the test result) be implemented in the Tooling API side?

You will see some options in that notification and follow one of them. e.g., update your Gradle version or re-choose a JVM to configure Gradle build.

@dboreham Thanks a lot for the help! As you know we just plan to solve these debugging related issues in the next month. I'm sorry I don't have enough time...