build: upgrade target file to use Eclipse 4.38

[rubenporras]

No description provided.

[rubenporras]

I do not know why LSP4E does not build with a target upgraded to Eclipse 4.38 and I have been looking at this already for a couple of hours. Any help would be appreciated.

[sebthom]

can you try https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/2025-12/ ?

[sebthom]

I am not a big fan of building only against Eclipse integration builds. If we do this, we end up releasing LSP4E versions that were never tested with the actual released Eclipse version. This can lead to unexpected errors and incompatibilities.

In TM4E, we use a matrix build that tests against three versions: the oldest supported Eclipse version, the latest stable Eclipse version, and the current Eclipse staging release. I know some people think this is too much work, but I disagree.

At the very least, we should test and develop against both the latest stable Eclipse version and the latest integration build.

[rubenporras]

@sebthom , I think this is the same as using latest, which is what we had in the repo until yesterday when I needed to switch it to have working builds.

I have now updated the PR to use latest, and it is failing again. I guess it has to do with the Junit 5 vs Junit 6 changes in eclipse 4.38 (see https://eclipse.dev/eclipse/markdown/?f=news/4.38/pde.md). I think we are seeing the item "Launch is executed by runs no tests or reports that no tests were found". @FlorianKroiss, could you take a look?

[rubenporras]

I am not a big fan of building only against Eclipse integration builds. If we do this, we end up releasing LSP4E versions that were never tested with the actual released Eclipse version. This can lead to unexpected errors and incompatibilities.

I agree, this was just me testing different combinations.

[FlorianKroiss]

I can take a look, but probably not before next week

[rubenporras]

That is great, don't worry, there is no rush.

[sebthom]

I had a same/similar issue in TM4E and solved it by setting <providerHint>junit5</providerHint>

				<plugin>
					<groupId>org.eclipse.tycho</groupId>
					<artifactId>tycho-surefire-plugin</artifactId>
					<version>${tycho-version}</version>
					<configuration>
						<!-- https://wiki.eclipse.org/Tycho/FAQ#How_to_use_SWTBot_or_some_UI_tool_for_testing.3F -->
						<useUIHarness>true</useUIHarness>
						<useUIThread>true</useUIThread>
						<argLine>-Xms512m -Xmx512m -Dfile.encoding=${project.build.sourceEncoding} ${tycho-surefire-plugin.vmargs}</argLine>
						<providerHint>junit5</providerHint>
					</configuration>
				</plugin>

[rubenporras]

I had a same/similar issue in TM4E and solved it by setting <providerHint>junit5</providerHint>

Thanks a lot, that was the solution.