Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327019

Summary:	Ensure breakpoint usage is consistent
Product:	[WebTools] JSDT	Reporter:	Michael Rennie <Michael_Rennie>
Component:	Debug	Assignee:	Project Inbox <jsdt.debug-inbox>
Status:	NEW ---	QA Contact:	Simon Kaegi <simon_kaegi>
Severity:	normal
Priority:	P3	CC:	browe, grant_gayed, thatnitind
Version:	3.3
Target Milestone:	Future
Hardware:	All
OS:	All
Whiteboard:	EaseOfUse
Bug Depends on:	289119, 292554, 308068, 308790, 310681, 311573, 314695, 318910, 321395, 306243, 315135, 315219, 318179, 323140, 324144
Bug Blocks:

Description Michael Rennie

2010-10-05 11:11:48 EDT

There are many failing scenarios for the use of breakpoints in the JSDT debugger. We must ensure that these failings are remedied with either a fix or better user feedback to explain that something failed.

There are three main themes to this:

1. make the setting of breakpoints more informed - ensure that if breakpoint placement fails there is sufficient user feedback to determine why

2. make sure breakpoints remain consistent with source - automatically update as source us edited (see bug 324144)

3. clean up the presentation of breakpoint options - for example 'suspend for all script loads' and 'suspend on all exceptions' could be better presented than a view sub-menu in the breakpoints view.