[jboss-dev] My logging ultimatum

[David M. Lloyd]

That is great... BUT... the two options should be: Use log4j with JUL
emulation, or use JUL with log4j emulation.  I'm not talking about what
JBossAS is using internally, but what it makes available to the user.

On Tue, 11 Dec 2007 19:51:41 -0800
Scott Stark <sstark at redhat.com> wrote:

> It should not be that big a change. There is a command line option to  
> enable this as the default jboss logger implementation. I have not  
> tested it in quite a while so I don't know if t still works.
> 
> 
> On Dec 11, 2007, at 1:29 PM, Jason T. Greene wrote:
> 
> > Good question :) If you want to get rid of a JAR, use the JDK  
> > logging API (writing your own wrapper) for your projects (no  
> > dependencies). Where jboss-common-logging gets interesting is that  
> > it provides a log4j appender framework for JDK logging on JBoss.  
> > This, IMO should be the default, but it's a major change for the AS.
> >
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development