Community
Participate
Working Groups
When an end user encounters a problem with Eclipse, it is important for support teams to be able to diagnose the root cause of the failure, and identify the failing plug-in. Eclipse should have enhanced error reporting tools that make it easy for end users to report problems. Tools should be available at all times, so that knowledgeable users could diagnose unexpected behavior such as slowdowns or exceptional memory use. [Platform Runtime, UI, SWT]
Maybe you should watch this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=124964
Marking as LATER as this item is defered for R3.2.
See also bug 144035.
Created attachment 48044 [details] List of possible themes and associated bugs for 3.3 Attempting to reopen this 'plan item' to see if we can do something for 3.3 ? :) Attached possibl elist of themes for 3.3 to be discussed, critiqued.. or shot :)
reopen so we can discuss :)
A new plan item in the 3.3 plan has been created to replace this. Since the new plan item has augmented wording, I'm going to close this one as a duplicate of the 3.3 plan item. Christophe and others, feel free to comment/CC on the new bug. *** This bug has been marked as a duplicate of 154090 ***