Re: Is log4cxx still alive?
Palic, Darko <darko.palic <at> gmx.de>
2012-01-26 16:12:52 GMT
I love log4cxx, because I love log4j and of course log4net.
There do you find a logging component which behaves nearly identically
with nearly identical config files? And so nearly every platform is
BUT, without active release cycles and a willing to integrate user
provided patches, the community will go away, even if the community
isn't already gone. From the users perspective the projects seems to be
What I am personally doing to check if I would invest effort into a new
component. I am first checking the release cycles. The second test is to
analyze the mailing list traffic. The third test is to check how fast
and often the developers response. Every factor says: the project is dead.
(Anyway I took the log4cxx, but on really long discussions with my
From the patching perspective, I have the same experiences like many of
you. We have also found some bugs, some of them have already been fixed,
but are only available as patches in the mailing list.
I could provide a patch, there we use shared mem for a high performance
syncing of multiple processes into one log destination. But I haven't
even tried it to provide the patch, since bugfixes haven't been
integrated for years.
We have solved it by making a "private fork" in our private repository,
there we've integrated the patches of the mailinglist. But this is a
damn stupid way!