Community
Participate
Working Groups
SnippetSupprotBreakpoint will be removed from the debug model as API. The snippet editor will use a "run-to-line" breakpoint instead, with a hit count of zero (so it is always hit, and does not appear in the breakpoint view). The tricky part is that the IType supplied to create the breakpoint does not exist in the workspace (i.e. it is a type in a the snippet support jar). We will have to make a dummy type that delegates to the underlying type handle, but provides an implementation for #getUnderlyingResource - to reutrn the project that the scrapbook is in. (the BP marker will be associated with the proejct that way - must have a resource for which to create marker on).
Fixed. Changed JavaLineBreakpoint.getResource(IType) to use the project resource for the type if the actual type does not exist as a resource. This simplifies the implemetnation (rather than making a dummy IType, which clients are not supposed to implement). Re-assigning for verification.
Please verify.
The refactoring looks good. However, there are still references to SnippetSupportLineBreakpoints in the XML. They appear to be unused, but when I tried to remove them, my snippet evaluations started failing. Also, it's unclear if but 5715 is related to this change.
Removed plug-in XML for Scrapbook breakpoints. Verified scrapbook evaluation works as before (new java.util.Date()).
Re-open to re-assign
Re-assigning.
There is still a marker definition for snippetSupportLineBreakpoint in org.eclipse.jdt.debug.plugin.xml. Is it there intentionally?
Removed reference. Re-tested and all is still good.
Verified. Looks good.
