[ANNOUNCEMENT] Apache Log4j 2.0-beta6 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta6 release!

Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides
many of the improvements available in Logback while fixing some inherent problems in Logback's
architecture.

This is the eighth release of Log4j 2 and is being made available to encourage use and feedback from the community.

Bug fixes and enhancements

Changes in this version include:

Fixed Bugs:
o LOG4J2-231:  Logger.getParent() was not returning the correct Logger. 
o LOG4J2-201:  Renamed Plugin annotation attribute from "type" to "category". 
o LOG4J2-219:  Fix: install default root logger if not configured (this is unchanged),
        but make sure to include configured named loggers. Clarified documentation. Thanks to Peter DePasquale. 
o LOG4J2-159:  Use OSGi version format in Fragment-Host 
o LOG4J2-234:  RegexFilter threw a NullPointerException when used as a context-wide filter. 
o LOG4J2-192:  Add support for interpolating Environment variables when processing the configuration. 
o LOG4J2-235:  Removed dependency on tools jar from core module, made jconsole dependency optional.
Thanks to Sebastian Oerding. 
o LOG4J2-233:  Fixed link to log4j-user mailing list. 
o LOG4J2-222:  Disruptor will now shutdown during Tomcat shutdown. Thanks to Steven Yang. 
o LOG4J2-224:  The FlumeAppender failed to start if the Flume RPCClient could not connect to any Flume
agents. 
o LOG4J2-223:  Fix LoggerContext start and stop to eliminate IllegalStateException and NoClassDefFound
errors. 
o LOG4J2-221:  Remove hundreds of compiler warnings. Thanks to Nick Williams. 

log4cx: attic or incubation?

Hello folks,

please look at these few e-mails:
http://mail-archives.apache.org/mod_mbox/logging-log4cxx-dev/201304.mbox/browser

For me there are two ways for log4cxx: incubation or attic.

I was outreaching for devs on log4cxx and got a few responses. It seems a couple
of people are interested in continuing this component. Most of them
said they might apply a couple of patches here and there, but nobody
burst out in emotions saying, YAY, this is it.

Without such a person I guess we have little chance in the incubator.
Maybe I am having a wrong view on it, so I ask you to voice your
opinion.

For now I would like to propose that I am cloning log4cxx to my GitHub
account and move the svn repos to the attic. That way I can overlook
if there is a team growing around log4cxx or not. Also I can ask for
ICLAs before accepting pull requests, which should help when we go
back to incubation. If there is, we can go back to incubation at any
time. If there is not, then well, no harm done.

Comments?

Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

[ANNOUNCEMENT] Apache Log4j 2.0-beta5 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta5 release!

Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides
many of the improvements available in Logback while fixing some inherent problems in Logback's
architecture.

This is the seventh release of Log4j 2 and is being made available to encourage use and feedback from the community.

Bug fixes and enhancements

Changes in this version include:

New features:
o LOG4J2-207:  Add JMX support. Thanks to Remko Popma. 
o LOG4J2-187:  Add tag library. Thanks to Nick Williams. 
o LOG4J2-164:  Add methods is/setEndOfBatch to LogEvent. Thanks to Remko Popma. 
o LOG4J2-163:  Add support for asynchronous loggers. Thanks to Remko Popma. 
o LOG4J2-179:  Add Logger interface APIs to log at given levels. 
o Added FlumePersistentManager which writes to BerkeleyDB and then writes to Flume asynchronously. 
o LOG4J2-155:  Expose file appender configuration details via an advertisement mechanism. 

Fixed Bugs:
o LOG4J2-205:  Fix deadlock in SocketAppender. Added option to not wait for socket reconnect. 
o LOG4J2-211:  Removing extra spaces in entry and exit method output. Thanks to Nick Williams. 
o LOG4J2-212:  Loggers without a "." had no parent logger. 
o LOG4J2-212:  Call LoggerContext.stop when the application is shutdown. 
o LOG4J2-210:  MapMessage was not enclosing key value in quotes when generating XML. Thanks to Arkin Yetis. 
o LOG4J2-198:  FlumeAvroManager now uses Flume RPCClient. 
o LOG4J2-196:  FlumeAvroManager now uses Flume RPCClient. 

Mirroring Log4J 2 on GitHub

Hey guys,

There's a Log4J mirror on GitHub at https://github.com/apache/log4j . Would it be possible to also mirror
Log4J2? 

We've recently switched to Log4J2 on one of the big projects that I am doing. Now we need to patch a few things
for our work in a way that is likely not going to be accepted back to Log4J. Specifically we want to
short-circuit Log4jLogEvent.getSource to return a fixed String. We are using AsynchAppender and
'Log4jLogEvent.getSource' is a noticeable performance bottleneck for us, and we currently don't see a
better way around it (ok, to be completely honest, we just don't have the cycles to refactor Log4J2
properly). So the idea was to keep a GitHub fork and merge periodically with the master copy.

Any thoughts/comments on exposing "2" on GitHub. 

As an Apache member I can probably ping infra myself. But wanted to talk to the 'logging' community first.

Thanks,
Andrus

Daily gump builds

Hey,

Is there an easy way to get my hands on the daily builds gump does for us? Maybe there is a documentation
somewhere that i haven't
found? Until now I crawled myself through here:

http://vmgump.apache.org/gump/public/index.html

without success.

Cheers,
Dominik

Moving log4cxx to the Attic

Hello

I would like to propose we move the log4cxx component to the attic.
I am not sure if the Apache Attic itself is the right place:
http://attic.apache.org/

as it seems to feed on TLDs only. I will ask there, if we agree that
log4cxx is not really maintained and that there will no work happen in
future.

I have hoped that there were a couple of people coming back to the
project when they see somebody is committing their patches. But it
hasn't happened and my own C skills are not enough to push this (time
is an issue too).

In case we agree, I would like to to keep the old log4cxx website,
saying this project is not longer maintained and the source code has
been moved to attic (if the attic.apache.org would take it). Other
options are also welcome, just let me hear what you think.

Best regards,
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

[ANNOUNCEMENT] Apache Log4j 2.0.beta4 released

Distribution directories

How to log to the Data Base

Please update your fingerprints on id

Hello folks,

if you are not listed here:
http://people.apache.org/keys/group/logging-pmc.asc

its time to go to id.apache.org and add your fingerprint. You'll then
appear in the file after a while.

Today I was looking at an issue with my key not here:
http://www.apache.org/dist/logging/KEYS

The file has much more names than in the link above, but not all
necessary. I believe we should use the option by id.apache.org for
log4j2. For now I will add my key to the old file too, so the issue
should be fixed

Cheers
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

Log4php git repository is live

Hi all,

Thanks to Gavin from Infra, our git repository is live as of today.
This marks the end of svn for log4php code. The svn repo will remain
available in read-only mode.

Here's the links you might need:

The official repository (and web interface), writable for developers:
https://git-wip-us.apache.org/repos/asf/logging-log4php.git

Official read-only mirror:
git://git.apache.org/logging-log4php.git

Github read-only mirror:
https://github.com/apache/logging-log4php

Note that the old apache and github mirrors, which were named
"log4php.git" instead of the current name "logging-log4php.git" will
be removed at some point in time, so don't use those for anything.

The github mirror is updated once daily. I was told that it's not
possible to update on commit since it's a mirror of the git.apache.org
mirror, and not of the main repository. I will look into possible ways
of improving this.

None of the other Logging Services projects are affected by this
change, except in a way to encourage them to move to git at some point
in time. The transition was very painless.

Best regards,
Ivan