Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] slf4j in indigo

Am 30.11.2010 03:42, schrieb Pascal Rapicault:
> However, given that slf4j seems to only support one binding at
> runtime, I'm wondering what is the recommended practice for using in
> Eclipse esp in the context of a platform rather than just a product.

If you stick to the SLF4J API you should be fine. The product assembler
could then select any binding it wants to support in its product. The
platform just uses the API.

At development time you can have the Logback bundles from Orbit in you
target platform. This allows wiring to the Logback binding. At
deployment time you just depend on the SLF4J API.

In an IDE you might get Logback from Orbit installed through p2.
Ideally, the IDE product would include a binding which logs all
warnings/errors/infos to the ".metadata/.log" file. But then it gets
difficult to change that at runtime because it's not possible currently
to uninstall/deactivate a bundle when an alternate bundle is installed.
(Some history in https://bugs.eclipse.org/bugs/show_bug.cgi?id=115042)

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/


Back to the top