You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to attach the debugger to a JVM 1.8 application, however the debugger's JVM version is 17, I suspect this is leading to wrong source mappings.
I am unable to use the Configure Java Runtime because it comes up blank. This stack trace is logged in OUTPUT whenever it tries to load:
Java Model Exception: Error in Java Model (code 969): webservices.rest does not exist
at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:562)
at org.eclipse.jdt.internal.core.JavaModelManager.getPerProjectInfoCheckExistence(JavaModelManager.java:2626)
at org.eclipse.jdt.internal.core.JavaProject.getPerProjectInfo(JavaProject.java:2358)
at org.eclipse.jdt.internal.core.JavaProject.getRawClasspath(JavaProject.java:2401)
at org.eclipse.jdt.launching.JavaRuntime.getVMInstall(JavaRuntime.java:423)
at org.eclipse.jdt.ls.core.internal.commands.ProjectCommand.getProjectSettings(ProjectCommand.java:119)
at org.eclipse.jdt.ls.core.internal.JDTDelegateCommandHandler.executeCommand(JDTDelegateCommandHandler.java:99)
at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler$1.run(WorkspaceExecuteCommandHandler.java:230)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler.executeCommand(WorkspaceExecuteCommandHandler.java:220)
at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$4(JDTLanguageServer.java:616)
at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:646)
at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Is there a way to configure the runtime to use with the debugger by modifying a config file, bypassing the Configure Java Runtime?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to attach the debugger to a JVM 1.8 application, however the debugger's JVM version is 17, I suspect this is leading to wrong source mappings.
I am unable to use the Configure Java Runtime because it comes up blank. This stack trace is logged in OUTPUT whenever it tries to load:
Is there a way to configure the runtime to use with the debugger by modifying a config file, bypassing the Configure Java Runtime?
Beta Was this translation helpful? Give feedback.
All reactions