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

Bug 340911

Summary:	Provide better exceptions and information when launching and debugging
Product:	[WebTools] JSDT	Reporter:	Michael Rennie <Michael_Rennie>
Component:	Debug	Assignee:	Project Inbox <jsdt.debug-inbox>
Status:	NEW ---	QA Contact:	Michael Rennie <Michael_Rennie>
Severity:	normal
Priority:	P3	CC:	grant_gayed, thatnitind
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Michael Rennie

2011-03-24 16:59:46 EDT

code from HEAD

Currently when an exception occurs we either trap it and eat it or we throw a general kind of exception and let the launch framework handle it. A good example of this is when you launch a remote debug session, if *anything* goes wrong we throw an IOException and let the platform launch framework handle - which surfaces as an error dialog and not-helpful message.

We should improve this by specializing exceptions so that we can handle them differently when different failure cases occur. For example if the connect timed for a remote debug session, we could throw a specialized exception that could be handled differently by the JavaScriptLaunchDelegate.