In a pattern I can’t figure out, sometimes when I click on a debug stack frame for an external class, Eclipse finds the source for the class but sometimes I get a window with just the text “Source not found” and a “Edit Source Lookup Path…” button. In the latter case, I can do a standard Eclipse “Open Type” operation, supply the class name, and Eclipse is able to find the source file (from a source jar file in the Gradle cache directory tree). So it’s puzzling why the logic that follows my clicking on the stack frame can’t find it.
I don’t know if this is a Buildship issue (I’ve seen misbehavior of this sort in the past in non-Buildship Eclipse environments), but I figured I’d ask here anyway.
Also, sometimes when the source can’t be found the “Source not found” window contains the text:
The JAR of this class file belongs to container ‘Project and External Dependencies’ which does not allow modifications to source attachments on its entries
with no “Edit Source Lookup Path…” button, which is even more aggravating because I don’t have the option to click the button to sort things out.
I haven’t figured out the pattern for why sometimes I get one type of “Source not found” window and sometimes I get the other type of “Source not found” window.