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.
I submitted a detailed review on #354
Essentially it seems that user-specified
sourcePathsare 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 returnjdt://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.