337147 – Warn the user when the launchingsupport jar is not available

Bug 337147 - Warn the user when the launchingsupport jar is not available

Summary: Warn the user when the launchingsupport jar is not available

Status:	NEW

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	Debug (show other bugs)
Version:	3.7
Hardware:	PC Windows 7

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	JDT-Debug-Inbox
QA Contact:

URL:
Whiteboard:	stalebug
Keywords:

Depends on:
Blocks:

Reported:	2011-02-14 12:44 EST by Michael Rennie
Modified:	2022-07-26 15:45 EDT (History)
CC List:	0 users

See Also:

Attachments
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

2011-02-14 12:44:52 EST

Version: 3.7.0
Build id: I20110208-0800

When the launchingsupport.jar file is missing we should report some kind of error / message to user. I just ran into a problem where the launchingsupport.jar file failed to get created in my workspace, which in turn caused 99% of the JDT debug tests to fail. It took me a good 10 minutes to figure out what was wrong.

Comment 1 Eclipse Genie

2020-06-07 12:14:07 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.

--
The automated Eclipse Genie.

Comment 2 Eclipse Genie

2022-07-26 15:45:32 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.

--
The automated Eclipse Genie.