Skip to content

Commit

Permalink
Non project classes caused setup_dap_main_class_configs to fail
Browse files Browse the repository at this point in the history
vscode.java.resolveMainClass returns ResolutionItems without projectName
for non project classes. Thus, calls to
vscode.java.resolveJavaExecutable resulted in "Index 1 out of bounds for
length 1". This cascaded into vscode.java.resolveClasspath failing with
"Failed to resolve classpath: Referenced classpath provider does not
exist: org.eclipse.m2e.launchconfig.classpathProvider".
  • Loading branch information
lbrayner committed Jan 10, 2024
1 parent 66b5ace commit 8e7dc82
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions lua/jdtls/dap.lua
Original file line number Diff line number Diff line change
Expand Up @@ -593,6 +593,10 @@ function M.fetch_main_configs(opts, callback)
util.execute_command({command = 'vscode.java.resolveMainClass'}, function(err, mainclasses)
assert(not err, vim.inspect(err))

mainclasses = vim.tbl_filter(function(mc)
return mc.mainClass and mc.projectName
end, mainclasses)

local remaining = #mainclasses
if remaining == 0 then
callback(configurations)
Expand Down

0 comments on commit 8e7dc82

Please sign in to comment.