Bug 184905 - [breakpoints] Breakpoint organizers should be qualified
Summary: [breakpoints] Breakpoint organizers should be qualified
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-01 11:53 EDT by Michael Rennie CLA
Modified: 2019-09-06 15:37 EDT (History)
0 users

See Also:

Attachments
screen shot (60.06 KB, image/png)
2007-05-01 11:56 EDT, Michael Rennie CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2007-05-01 11:53:58 EDT 
When the option to Show qualified names it turned on in the breakpoints view it should apply to the breakpoint organizers where appropriate.

Consider the following example:

1. I have a project P1 with a source file Test in package a
2. I have a project P2 with a source file Test in package a
3. I turn on show qualified names, and set the breakpoint organizer to be 'Files'

I then wind up with what appears to be two Test.java groups with similar naming for the breakpoint within them, even though they are two different files.

See the attached screenshot, each of the Test.java orgaqnizers should be project qualified to distinguish them.
Comment 1 Michael Rennie CLA 2007-05-01 11:56:43 EDT 
Created attachment 65481 [details]
screen shot

shows the two sets that can not be distinguished
Comment 2 Darin Wright CLA 2007-05-01 22:25:43 EDT 
Not planned for 3.3
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:37:34 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.