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

Bug 145332

Summary:

[hierarchy] Error trace should log offending unit and trace

Product:

[Eclipse Project] JDT

Reporter:

Philipe Mulet <philippe_mulet>

Component:

Core

Assignee:

JDT-Core-Inbox <jdt-core-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

Version:

3.2

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
Proposed change	none

Description Philipe Mulet

2006-06-05 08:55:02 EDT

Build 3.2RC6

While fixing bug 144976, I noticed the .log did not contain any valuable information in presence of AbortCompilation exceptions (being silently caught).

Also when dumping/logging, it should mention the name of the offending unit which cannot be connected (may be different from focus).

Comment 1 Jerome Lanneluc

2006-06-08 06:41:59 EDT

Created attachment 43850 [details]
Proposed change

Comment 2 Philipe Mulet

2006-06-08 07:40:50 EDT

Shouldn't it log only in DEBUG mode ? Being resilient is part of the normal deal, so logging then might be overkill (and scare end user).

Comment 3 Jerome Lanneluc

2006-10-02 10:32:47 EDT

Comment on attachment 43850 [details]
Proposed change

Patch can no longer be applied to HEAD. Marking as obsolete.

Comment 4 Jerome Lanneluc

2008-05-12 05:25:55 EDT

Post 3.4

Comment 5 Eclipse Genie

2019-10-12 03:39:02 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.