Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 102548 - [breakpoints] Method Entry Breakpoint signature does not adapt
Summary: [breakpoints] Method Entry Breakpoint signature does not adapt
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-02 02:50 EDT by Ed Willink CLA
Modified: 2009-08-30 02:35 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2005-07-02 02:50:43 EDT
A method entry breakpoint retains its associated signature after a manual change
of that signature. (The breakpoints display shows the old signature).
e.g manual edit of getFeatureTypes(Class factoryClass, Object instance) to
getFeatureTypes(Class factoryClass).

This is perhaps correct, since it was not refactored.

However the start of line breakpoint marker appears to indicate that the changed
method has an associated breakpoint, when it doesn't.

a) the start of line marker should be removed
b) the method entry breakpoint should be 'grayed' out.
Comment 1 Darin Wright CLA 2006-04-17 15:32:43 EDT
Deferred
Comment 2 Eclipse Webmaster CLA 2009-08-30 02:35:27 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.