pax-logging (Was: Should 4.2.11 applications run on 4.3.0?)

[Steinar Bang <sb...@dod.no>]

>>>>> Steinar Bang <sb...@dod.no>:
>>>>> Jean-Baptiste Onofre <jb...@nanthrax.net>:

>> Instead of using LogService, you can use slf4j (and so pax-logging), and you won’t have the core dependency (at least for logging).

> Actually I think using the logservice is simpler... slf4j and the
> various config files to make logs appear and disappear, have always been
> a mystery to me...

[snip!]
> But if there is a pax-logging, it sounds like it's something I should
> check out.

> So I'll do that.

So basically: you use slf4j in your code, but the actual logging
mechanism is the OSGi LogService?
 https://ops4j1.jira.com/wiki/spaces/paxlogging/overview

That means that all the obscure config files (which belongs to
the underlying logging logging system, e.g. Logback or Log4J, rather
than slf4j) becomes irrelevant for production code.

So that's nice.

Also, the slf4j API is well known and much nicer than the LogService
one.  Much nicer for others working on my code.

However, LogService gave me the possibility of asserting on log messages
in JUnit tests, something I've never been able to do with the regular
logging frameworks.

And I have lots of tests doing it.

Also, I'm using LogService throughout my code and it would be a lot of
work to change it.

(losing the osgi.core maven dependency isn't a big deal for me. I just
wondered why I needed it...?)