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

Bug 332152

Summary:	Exceptions logged in FrameworkLog do not show up in the 'Error Log' view immediately
Product:	[Eclipse Project] PDE	Reporter:	Remy Suen <remy.suen>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	john.arthorne, tjwatson
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	292135
Bug Blocks:

Description Remy Suen

2010-12-08 11:50:38 EST

This is because the 'Error Log' view uses an ILogListener, which is for events logged with an ILog. In 4.x, our logging mechanism is backed by the OSGi FrameworkLog so no notifications are fired off.

Using ILog ties us into the org.eclipse.core.runtime bundle and also effectively "forces" the bundle's activator to extend the Plugin class.

Any thoughts on this matter, John?

Comment 1 John Arthorne

2010-12-08 16:18:41 EST

Sounds like a bug in the error log view. This certainly isn't unique to e4 - most of Equinox, including the framework and p2, exclusively use FrameworkLog so they would have the same problem.

Comment 2 Thomas Watson

2010-12-08 16:23:34 EST

This would get solved by a solution proposed in bug292135 where I am proposing the use of the OSGi LogService to aggregate and unify all the logging stories within Eclipse.

Comment 3 Thomas Watson

2011-01-10 09:57:13 EST

This should be fixed with the changes in bug292135.

*** This bug has been marked as a duplicate of bug 292135 ***