I think that would be good. I'd like to see what we all think about a more comprehensive life cycle state machine that works more like how LoggerContext does. I'm working on a patch proposal for that, but it is a non-trivial change that affects lots of classes in log4j-core. If this seems like a good idea, it might be a good idea to get this in before RC2 as well.
On 7 April 2014 15:42, Gary Gregory <garydgreg...@gmail.com> wrote: > I've just figured out how to workaround a Jackson bug in order to do XML > and JSON server socket receivers. > > We can wait for me to get this in this week (hopefully) for RC2, or not :) > > Gary > > > On Mon, Apr 7, 2014 at 11:35 AM, Matt Sicker <boa...@gmail.com> wrote: > >> There's been a bunch of work done since RC1. It might be a good idea to >> get another release candidate going. >> >> -- >> Matt Sicker <boa...@gmail.com> >> > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second > Edition<http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- Matt Sicker <boa...@gmail.com>
