The filename of the class(with source code included) should not end with `.class` on debugging scene

[mozhuanzuojing]

When we normally open a class with source code, its filename ends with .java. However, if we jump to a class with source code during debugging, the filename ends with .class. This results in the same class being opened twice (one ending with .java and the other with .class), which is very confusing. Could we standardize this behavior? If a class has source code, it should always be opened as a file ending with .java.

[mozhuanzuojing]

Meanwhile, a breakpoint has been set in the .java file (the Java source file of the class), but during debugging, the execution jumps to and breaks at the .class file instead. The breakpoint symbol is not displayed, yet it actually takes effect. This issue occurs because the same class has been opened with different file extensions.

[datho7561]

Do you have a simple project that you can include that recreates the problem?

I created a simple Maven project (Hello world, except there's a second class with a utility method that returns the string "hello world"). When I debug into the utility class, it opens with the extension .java as expected. If there's a copy of the file already open, it navigates to that file.

Based off what you've told me, one possibility is that the compiled copy of the class that opens as .class is out of date with the source copy, and that you need to recompile before debugging. Do you have autobuilding disabled?

[mozhuanzuojing]

[mozhuanzuojing]

Based off what you've told me, one possibility is that the compiled copy of the class that opens as .class is out of date with the source copy, and that you need to recompile before debugging. Do you have autobuilding disabled?

@datho7561
autobuilding is enabled(default). this is an example. Thank you for your concern about this issue. It has actually existed for many years; it just wasn’t brought up until now.

jumpClass2.zip

[datho7561]

Yep. I can reproduce this now. I guess eclipse.jdt.ls and https://github.com/microsoft/java-debug must use slightly different mechanisms to generate the read-only file meant to represent the class. This recent change: 25d3d78 is what uses the .java extension instead of .class on the eclipse.jdt.ls side (so that sources for compiled files with Kotlin sources can be displayed with proper syntax highlighting). java-debug probably needs to adapt to that change. Based off what you've told me there'll be more to it than that though.