Bug 248794

Summary:	[plan] Logging
Product:	[Eclipse Project] Equinox	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	Components	Assignee:	equinox.components-inbox <equinox.components-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	caniszczyk, simon_kaegi, tjwatson
Version:	3.5	Keywords:	plan
Target Milestone:	3.5 M7
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Jeff McAffer

2008-09-26 17:49:56 EDT

To date the platform has placed tight restrictions on the configuration of existing 3rd party logging frameworks. The goal here is to lift the most important of these restrictions and provide a modular and OSGi friendly integrated approach.

Comment 1 Thomas Watson

2009-05-28 14:18:03 EDT

Simon, is new log service implementation a step to addressing this bug?

Comment 2 Chris Aniszczyk

2009-05-28 14:19:46 EDT

fyi, there's an e4 logging bug open too. whatever is done in e4, should be this.

Comment 3 Simon Kaegi

2009-05-28 14:33:31 EDT

Yes, the new log service is a step in this direction and graduating it is all we planned for in 3.5.

The deeper integration work to play with the Eclipse Log could potentially be done for 3.6 but Chris is correct in that we're more concretely looking at doing something in e4 and it's likely to involve the log service we've graduated in 3.5.

Comment 4 Thomas Watson

2009-05-28 14:48:57 EDT

(In reply to comment #3)
> Yes, the new log service is a step in this direction and graduating it is all
> we planned for in 3.5.
> 
> The deeper integration work to play with the Eclipse Log could potentially be
> done for 3.6 but Chris is correct in that we're more concretely looking at
> doing something in e4 and it's likely to involve the log service we've
> graduated in 3.5.
> 

Closing this as fixed for 3.5 since we did all that was planned and graduated the new logging impl in M7.