Community
Participate
Working Groups
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.
Simon, is new log service implementation a step to addressing this bug?
fyi, there's an e4 logging bug open too. whatever is done in e4, should be this.
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.
(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.
