Home » Language IDEs » Java Development Tools (JDT) » Breakpoint in debugged application doesn't show source file, after upgrade to 2020-03
| Breakpoint in debugged application doesn't show source file, after upgrade to 2020-03 [message #1823120] |
Thu, 19 March 2020 17:04  |
 David M. Karr
Messages: 801
Registered: July 2009 |
Senior Member |
|
|
I've been using 2019-12 since the release, and just upgraded to 2020-03 yesterday.
I run in debug our Maven SpringBoot applications quite often. Stepping through the code works perfectly fine, before today.
Today I ran one application in debug that I've run many times. It started up fine, but when it hit a breakpoint that I set, it was not able to find the source. I inspected the run configuration, and it specifies the correct project. The project itself looks like a normal Maven project in the package explorer. It shows the correct source folders, and there are no errors.
I even tried clicking "Edit Source Lookup Path". The "Default" entry has all the maven dependencies and one folder that we always manually add to our springboot run configurations (a folder with additional properties files). There were no source folders. I then manually added the project to the source lookup and inspected the result. It appeared to have all the relevant folders from that project. However, even after I closed the editor window for the file and reopened it from the stack entry, it still said it can't find the source file.
I checked the error log. I saw a string of exceptions about a hover problem in Spring IDE (which I will report), but nothing that would cause the problem I'm seeing.
|
|
| | | | | |
| Re: Breakpoint in debugged application doesn't show source file, after upgrade to 2020-03 [message #1826432 is a reply to message #1826424] |
Fri, 24 April 2020 18:10  |
Shawn Stamey
Messages: 4
Registered: April 2020 |
Junior Member |
|
|
David, you're right on the symptoms and timeline (I was focused on the problem and neglected to notice it was a 2017 issue), but what caught my eye was the description of the bug:
"The bug is located in StandardSourcePathProvider. The Maven container (MavenClasspathContainer) is resolved with JavaRuntime.resolveRuntimeClasspathEntry(...), which produces a runtime classpath (output locations) instead of a source lookup path (project references)."
When I open Debug Configurations -> Source tab and expand "Default" entry, and compare 2019-12 with 2020-03 I see what appears to be this same kind of issue.
- On 2019-12, under Default I see my project names: "endpoint.tests"
- On 2020-03, under Default I see "classes - \endpoint.tests\target"
So maybe it is technically a different bug and maybe this needs a different fix, but it is essentially the same mixup happening, Eclipse is being told to search the class files in the project instead of the source code in the project.
|
|
| | |
Goto Forum:
Current Time: Fri Apr 19 07:15:58 GMT 2024
Powered by FUDForum. Page generated in 0.01572 seconds |
] 
Search
Help
Register
Login
Home
