| Diagnosing error due to "missing Java project context" upon hitting conditional breakpoint [message #1798377] |
Fri, 16 November 2018 07:40  |
Eclipse User |
|
|
|
I'm using 2018-09 and have imported a Maven project using m2e. The project contains a Java application that I have launched using Debug As -> Java Application. I've configured a conditional breakpoint in one of the project's dependencies. When it is hit, an error occurs with the reason "Unable to compile conditional breakpoint - missing Java project context".
I think the error is probably due to a bug in JDT or M2E but I'm not sufficiently familiar with either project to track it down. I'm hoping that someone here can give me some pointers please. I have things set up so that I can debug the workspace where the error is occurring. I've been stepping through JavaLineBreakpoint where it tries to resolve the project and have seen that it cannot do so, but that's about as far as I've got.
One other thing that I've noticed that may be relevant is that the tab that opens to show the source of the file where the breakpoint is set is a .java file with a hollow J. The breakpoint also doesn't appear in the gutter. When I opened the class to set the breakpoint, the tab that opened was for a .class file with the binary icon and a solid J in the top-left corner.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03638 seconds
Home