You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Dennis Lundberg <de...@mdh.se> on 2005/12/11 13:47:28 UTC
Re: [logging] What's needed for a release
Dennis Lundberg wrote:
> robert burrell donkin wrote:
>> On Mon, 2005-11-14 at 00:22 +0100, Dennis Lundberg wrote:
>>
>> <snip>
>>
>>> 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?
>
> I've just tried with the latest code. Trace-level logging is now working
> correctly with log4j 1.2.12 and 1.2.13rc1.
Just a quick follow-up: log4j 1.2.13 has been released so I ran my tests
on that version as well with the following results:
2005-12-11 13:32:57,805 FATAL org.apache.commons.logging.Verify -
Logging at FATAL level.
2005-12-11 13:32:57,825 ERROR org.apache.commons.logging.Verify -
Logging at ERROR level.
2005-12-11 13:32:57,825 WARN org.apache.commons.logging.Verify -
Logging at WARN level.
2005-12-11 13:32:57,825 INFO org.apache.commons.logging.Verify -
Logging at INFO level.
2005-12-11 13:32:57,825 DEBUG org.apache.commons.logging.Verify -
Logging at DEBUG level.
2005-12-11 13:32:57,825 TRACE org.apache.commons.logging.Verify -
Logging at TRACE level.
As you can see all is well also with the official release.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] What's needed for a release
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sun, 2005-12-11 at 13:47 +0100, Dennis Lundberg wrote:
> Dennis Lundberg wrote:
<snip>
> Just a quick follow-up: log4j 1.2.13 has been released so I ran my tests
> on that version as well with the following results:
>
> 2005-12-11 13:32:57,805 FATAL org.apache.commons.logging.Verify -
> Logging at FATAL level.
> 2005-12-11 13:32:57,825 ERROR org.apache.commons.logging.Verify -
> Logging at ERROR level.
> 2005-12-11 13:32:57,825 WARN org.apache.commons.logging.Verify -
> Logging at WARN level.
> 2005-12-11 13:32:57,825 INFO org.apache.commons.logging.Verify -
> Logging at INFO level.
> 2005-12-11 13:32:57,825 DEBUG org.apache.commons.logging.Verify -
> Logging at DEBUG level.
> 2005-12-11 13:32:57,825 TRACE org.apache.commons.logging.Verify -
> Logging at TRACE level.
>
> As you can see all is well also with the official release.
great :)
thanks
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org