getting Errors running builder 'CDT Core Builder' after recent update to 4.34

[emaayan]

after updating eclispe to 4.34 which includes java aduptium 23

C/C++ CMake Build Support - Preview	11.6.1.202406241230
C/C++ Common GDB Support	11.6.1.202406241230
C/C++ Development Platform	11.6.1.202407022008
C/C++ Development Tooling Native Utilities	11.6.1.202407022008
C/C++ Development Tools	11.6.1.202407022008
C/C++ DSF GDB Debugger Integration	11.6.1.202406241230
C/C++ GNU Toolchain Build Support	11.6.1.202406241230
C/C++ GNU Toolchain Debug Support	11.6.1.202406241230
C/C++ LSP Support	2.1.0.202501232153

i'm getting the following in trying to build

java.lang.NoSuchMethodError: 'java.util.stream.Stream org.eclipse.cdt.lsp.util.LspUtils.getLanguageServers()'
	at com.espressif.idf.core.util.LspService.<init>(LspService.java:27)
	at com.espressif.idf.core.build.IDFBuildConfiguration.runCmakeBuildCommand(IDFBuildConfiguration.java:489)
	at com.espressif.idf.core.build.IDFBuildConfiguration.build(IDFBuildConfiguration.java:355)
	at org.eclipse.cdt.core.build.CBuilder.build(CBuilder.java:45)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:1077)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:296)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:352)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:441)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:444)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:403)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:668)
	at org.eclipse.core.internal.resources.Project$1.run(Project.java:604)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2457)
	at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:642)
	at org.eclipse.core.internal.resources.Project.build(Project.java:154)
	at org.eclipse.debug.core.model.LaunchConfigurationDelegate.lambda$0(LaunchConfigurationDelegate.java:415)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2457)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2477)
	at org.eclipse.debug.core.model.LaunchConfigurationDelegate.buildProjects(LaunchConfigurationDelegate.java:421)
	at org.eclipse.debug.core.model.LaunchConfigurationDelegate.buildForLaunch(LaunchConfigurationDelegate.java:122)
	at org.eclipse.launchbar.core.target.launch.LaunchConfigurationTargetedDelegate.superBuildForLaunch(LaunchConfigurationTargetedDelegate.java:61)
	at com.espressif.idf.launch.serial.internal.SerialFlashLaunchConfigDelegate.buildForLaunch(SerialFlashLaunchConfigDelegate.java:270)
	at org.eclipse.launchbar.ui.internal.commands.BuildActiveCommandHandler$1$1.run(BuildActiveCommandHandler.java:110)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

eclipse.buildId=unknown
java.version=23.0.1
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86_64 -clean

[jonahgraham]

@emaayan this is one for Espressif. The error comes from them calling non-API code in CDT-LSP. There will be a warning in the com.espressif.idf.core.util.LspService Java file that it is accessing non-API code. Or there would be such a warning if they hadn't expressly suppressed the warning.

You can point them at #370 where the internal code of CDT LSP was modified.

Fortunately you have tested a pre-release of CDT LSP for them so you detected this early for them. I assume you installed CDT LSP from https://download.eclipse.org/tools/cdt/builds/cdt-lsp/main/ ? However I don't see how the Eclipse and Java version updates affects this issue, unless you also got the new CDT LSP from the builds location at the same time. I recommend as a workaround for now you use the release CDT LSP 2.0 version until Espressif can provide an update.

[emaayan]

i was using lsp version with a console for another bug i have about markers.

[jonahgraham]

Thanks for testing marker issues - unfortunately it looks like you'll have to test that without Espressif installed.

Thanks for filing the issue with Espressif espressif/idf-eclipse-plugin#1127

[ghentschke]

I'll close this issue since it's an Espressif issue and occurred due to a test @emaayan did thankfully for me!