Thank you for your comments. Let me respond to each in turn.
1) For your information, as of version 0.9.18 released a few days ago,
logback is dual-licensed under both the LGPL *and* the EPL (Eclipse
Public License).
2) Logback is driven by a BDFL, that would me, following many of the
open-source principles prevalent at the ASF. The working relationships
within logback community, with at least 5 active participants from
different horizons, are very good if not excellent. You are welcome to
join and I think you should.
3) Indeed, many ASF projects are using log4j although a significant
percentage uses SLF4J with log4j as the underlying framework/back-end.
Until recently, those projects could *not* have used logback as the
underlying framework but that has changed. In light of the recent
licensing changes, I would expect many ASF projects to migrate to
logback, as it is objectively a better log4j.
4) The argument of complexity is quite interesting. I can tell you
that as time passes, the tendency is to have more complex code. For
example, users are calling for a more complex API (but also more
flexible) within logback internals. As you know, the client API, i.e
SLF4J, is already cast in stone and is very unlikely to change.
Anyway, I would be interested to learn about your suggested changes
or simplifications within the context of the logback project.
Cheers,
Christian Grobmeier wrote:
Hi Ceki,
thanks for pointing me to logback. But there are several reasons I
would like to keep Log4J alive.
1) logback is distributed as LGPL, not Apache License. Both are
compatible, but I prefer ASL.
2) logback is driven by a company and not an ASF project, which I
prefer for several reasons
3) so much users are still using Log4J, including lots of Apache projects
4) old log4j and logback api feels a bit complex to me. I think both
could be more simple
That being said, logback is not an option for me at the moment nor was
it necessary to use any of the new features it provides (speaking only
of my own projects of course). This is why I would like to see a
continuation on the log4j work.
Best regards,
Christian
On Fri, Dec 11, 2009 at 11:02 AM, Ceki Gülcü <[email protected]> wrote:
Hi Christian,
Have a look at logback. It is the continuation of the log4j 1.3
effort, with 4 years of additional work.
--
Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
