*** Issue 34681 has been marked as a duplicate of this issue. ***

OK, let's come up with suggestions.

There are a few other priorities to attend to at the moment, but just
wanted to capture some of the discussion i've had with Martin on this
subject for future reference. This isn't the final solution, and will
have to be worked on more. 

My first suggestion is that in the Tools | Options window, that only
one Breakpoint should show up under the Editing category. All the
other breakpoints (e.g. the underlying implementation is Java
breakpoint, JSP breakpoint, JSP/Servlet Breakpoint) should just use
the same representation. (For example, I have a preference to show the
breakpoint foreground as neon blue. So i change the foreground of
"Breakpoint" to blue.  All breakpoints should use neon blue) I'm not
sure if this is a major implementation issue, but it would be a very
nice UI win for the user, in that users don't have to scratch their
head figuring out what each type of breakpoint means.

Here's more info from Martin:
>I'd like to remove the JSP/Servlet breakpoint, but there >are some
problems with this. My perspective is that JSP >Breakpoint stays as it
is now, but it's presence in the Add >breakpoint window will be: 
'JSP' and type 'Line' - to be >consistent with other (java)
breakpoints. I'm trying to use >the Java breakpoints instead of
JSP/Servlet, but I'm still >not sure if that will be possible and will
not lead to any >future problems. As a possible part-solution, I think
we >could use the JSP category for both JSP and JSP/Servlet, >and for
JSP the type would be 'JSP Line' or 'JSP line >breakpoint', and for
servlet it would be 'Servlet line'.
>
>> Also, in S1S5, I see "JSP Breakpoint" and "Pink JSP >>Breakpoint".
Not sure why both exist.
>
>Well, I didn't choose the names, I used the old ones ;O) >because I
couldn't find anything more reasonable and less >confusing than 'pink'
;O).
>The Pink JSP breakpoint is an annotation of placeholder for >servlet
breakpoint - when you place a breakpoint into a >servlet, it is shown
in corresponding jsp, too. And that's >what pink jsp breakpoint
annotations are for (their pink is >more pink than the other
breakpoints' pink ;O) ). I assume >that pink JSP breakpoint annotation
will have to stay, >unless we want to stop showing the breakpoint
placeholders. >But we certainly have to choose some other annotation name.
>
> Martin 

Well, the suggestion is doable and easy - all our breakpoints would
just use 'Breakpoint' and 'Disabled breakpoint' annotations provided
by debuggercore. 

 But I think it would be confusing to the user - currently - user
places a breakpoint into the servlet, and it is shown also in the
corresponding jsp as a 'light' breakpoint (because it is removed when
the jsp changes).

 With the suggested change, all the breakpoints in the jsp would look
the same, but only some of them (and the user can't see which ones)
will be removed magically when the jsp is changed.

Well, if the breakpoints are going to disappear when the
servlet is changed anyway, that's the confusing part, not
what name/color they have.  Just call its
"Servlet breakpoint in JSP" or something like that if you
have to call it something.  

Suggestion:  
 - Remove/hide the system option for the "Pink" breakpoints
 - Use whatever color is specified for the servlet breakpoint
   for the JSP, but do something like Color.brighter() to
   make it visibly different.  The point is the user 
   shouldn't need to decide

we don't have pink jsp breakpoints in 3.6

Verified assuming reporter agrees with resolution.