commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@blueyonder.co.uk>
Subject Re: [logging] What's needed for a release
Date Thu, 17 Nov 2005 21:59:38 GMT
On Mon, 2005-11-14 at 00:22 +0100, Dennis Lundberg wrote:

<snip>

> OK. I've set up a verification environment. I have built JCL 1.1-dev 
> from SVN at revision 343981. Also I had to build log4j 1.2.13rc1 from 
> SVN as I couldn't find a distribution for it.

great :)

thanks

> The logging implementation is selected in commons-logging.properties 
> like this
> org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4J12Logger
> or like this
> org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4J13Logger
> 
> Log4j is configured via a log4j.xml file, except for 1.2.6 which only 
> supports properties file configuration.
> 
> Here are the (disappointing) results:
> 
> 1.2.6: log4j.rootCategory=TRACE
> 2005-11-13 23:51:59,444 FATAL org.apache.commons.logging.Verify - 
> Logging at FATAL level.
> 2005-11-13 23:51:59,444 ERROR org.apache.commons.logging.Verify - 
> Logging at ERROR level.
> 2005-11-13 23:51:59,444 WARN  org.apache.commons.logging.Verify - 
> Logging at WARN level.
> 2005-11-13 23:51:59,444 INFO  org.apache.commons.logging.Verify - 
> Logging at INFO level.
> 2005-11-13 23:51:59,444 DEBUG org.apache.commons.logging.Verify - 
> Logging at DEBUG level.
> 2005-11-13 23:51:59,444 DEBUG org.apache.commons.logging.Verify - 
> Logging at TRACE level.
> 
> 1.2.12: <level value ="trace" />
> 2005-11-14 00:03:03,919 FATAL org.apache.commons.logging.Verify - 
> Logging at FATAL level.
> 2005-11-14 00:03:03,939 ERROR org.apache.commons.logging.Verify - 
> Logging at ERROR level.
> 2005-11-14 00:03:03,939 WARN  org.apache.commons.logging.Verify - 
> Logging at WARN level.
> 2005-11-14 00:03:03,939 INFO  org.apache.commons.logging.Verify - 
> Logging at INFO level.
> 2005-11-14 00:03:03,939 DEBUG org.apache.commons.logging.Verify - 
> Logging at DEBUG level.
> 2005-11-14 00:03:03,939 DEBUG org.apache.commons.logging.Verify - 
> Logging at TRACE level.
> 
> 1.2.13rc1: <level value ="trace" />
> 2005-11-14 00:08:13,715 FATAL org.apache.commons.logging.Verify - 
> Logging at FATAL level.
> 2005-11-14 00:08:13,715 ERROR org.apache.commons.logging.Verify - 
> Logging at ERROR level.
> 2005-11-14 00:08:13,715 WARN  org.apache.commons.logging.Verify - 
> Logging at WARN level.
> 2005-11-14 00:08:13,715 INFO  org.apache.commons.logging.Verify - 
> Logging at INFO level.
> 2005-11-14 00:08:13,715 DEBUG org.apache.commons.logging.Verify - 
> Logging at DEBUG level.
> 2005-11-14 00:08:13,715 DEBUG org.apache.commons.logging.Verify - 
> Logging at TRACE level.
> 
> 1.3alpha-7: <level value ="trace" />
> 2005-11-13 23:52:37,669 FATAL org.apache.commons.logging.Verify - 
> Logging at FATAL level.
> 2005-11-13 23:52:37,669 ERROR org.apache.commons.logging.Verify - 
> Logging at ERROR level.
> 2005-11-13 23:52:37,669 WARN  org.apache.commons.logging.Verify - 
> Logging at WARN level.
> 2005-11-13 23:52:37,669 INFO  org.apache.commons.logging.Verify - 
> Logging at INFO level.
> 2005-11-13 23:52:37,669 DEBUG org.apache.commons.logging.Verify - 
> Logging at DEBUG level.
> 2005-11-13 23:52:37,669 TRACE org.apache.commons.logging.Verify - 
> Logging at TRACE level.
> 
> 
> As you can see above, trace level support is *not* working in either 
> 1.2.12 or 1.2.13rc1. Am I doing something wrong here?

i set up a test harness quickly in eclipse and i get something very
similar. i think that this issue is caused by buggy reflection: it's
safer to use Level.class than Priority.class.

could you give the latest code a try?

TIA

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message