What's the motivation behind this? Just dropping log4j? It seems to
me that we'd want to provide some way for the tons of crap still using
log4j to still log to the log file properly.
- DML
On Tue, 11 Dec 2007 21:45:10 -0800
Scott Stark <sstark(a)redhat.com> wrote:
This was using JUL with log4j like loggers/xml configuration. JUL
would
be what is available to users, and they would have the jboss intalled
log4j type of loggers. Need to pull together what I'm talking about and
update this page as its not describing the --log=jdk option I added;
http://wiki.jboss.org/wiki/Wiki.jsp?page=Logging
succubus:bin starksm$ ./run.sh -help
...
-l, --log=<log4j|jdk> Specify the logger plugin type
David M. Lloyd wrote:
> 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(a)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.
>>
>>
>>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development