sourcePaths no longer work after #354

[puremourning]

I submitted a detailed review on #354

Essentially it seems that user-specified sourcePaths are no longer used when resolving the filesystem path for a file in the stack trace after the above patch. The result is that we always return jdt:// paths which not all clients know how to handle.

It seems to me that we should always prefer filesystem paths (having applied user sourcePaths) over "internal" jdt:// paths.

[puremourning]

One solution might be an option to ask the server to never return a .class file jdt:// path and always return from the sourcePaths or "unknown"

[github-actions]

Hi Ben Jackson (@puremourning), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

• It appears there is no existing fix for Expose a command to resolve the source mapping for the specified stacktrace #354; the debugger always returns jdt:// URIs and ignores user sourcePaths.
• As a temporary workaround, you can configure VS Code’s java.project.sourcePaths (in settings.json) to include your sources so the language server can resolve filesystem paths even if the debugger emits jdt:// URIs.
• Please file a new issue on the java-debug repo (https://github.com/microsoft/java-debug/issues) referencing PR Expose a command to resolve the source mapping for the specified stacktrace #354 and this report, requesting that the debugger prefer resolved filesystem paths (after applying user sourcePaths) over jdt:// URIs.

Other references with low confidence

• sourcePaths in "java.test.config" not working
  • Explains that java.test.config.sourcePaths is for dependency sources, whereas java.project.sourcePaths defines project structure. Might help clarify which setting to use.
  • URL: sourcePaths in "java.test.config" not working vscode-java-test#1552 (comment)

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[puremourning]

'Shortly'? It's been Ignored for 3 years, bot. I'm not sure I'll live long enough to see this resolved.

[javanoo6]

'Shortly'? It's been Ignored for 3 years, bot. I'm not sure I'll live long enough to see this resolved.

damn bro this is hecking bad to see. The habibis from jdtsl actually patch stuff quickly. Nevertheless, I also found issue: when project has both pom and gradle this java-debug fails to correctly resolve where the heck main class is.

[puremourning]

I stand corrected! Thanks for the fix :)