logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Smith <psm...@aconex.com>
Subject Re: JUL appender
Date Sun, 08 Jul 2007 22:30:49 GMT
New snapshot setup here:






I've added attribution to you in the changes.xml and list of  
contributors.  Let me know if you'd rather have your name removed (or  
info update).


On 08/07/2007, at 4:49 PM, Sagi Mann wrote:

> Nice catch!
> Thanks for helping out with the investigation.
> Could you pls point me to the proper snapshot URL?
> Thanks,
> Sagi
> ________________________________
> From: Paul Smith [mailto:psmith@aconex.com]
> Sent: Friday, July 06, 2007 06:22 AM
> To: Log4J Developers List
> Subject: Re: JUL appender
> finally worked it out.  mvn test runs do not run in isolated
> classloaders so a prior test case had added another JULAppender to the
> logger configuration, which was using a different level converter.  I
> couldn't work out why TRACE was being mapped to INFO until I
> toStringed the appender on the doAppend loop.
> Looks much better.
> the jul bridge release will depend on a 1.2.15 and companion official
> release.  Once they are officially signed off a vote can be taken to
> vote on the bridge being released.  It would be nice if you could grab
> the latest snapshot build and confirm the behavior works to your
> satisfaction?
> The problem is that the people.apache.org site is down so I can't
> publish a new snapshot distro for testing:
> http://monitoring.apache.org/status/
> cheers,
> Paul
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org

Paul Smith
Core Engineering Manager

The easy way to save time and money on your project

696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200  Fax: +61 3 9240 0299
Email: psmith@aconex.com  www.aconex.com

This email and any attachments are intended solely for the addressee.  
The contents may be privileged, confidential and/or subject to  
copyright or other applicable law. No confidentiality or privilege is  
lost by an erroneous transmission. If you have received this e-mail  
in error, please let us know by reply e-mail and delete or destroy  
this mail and all copies. If you are not the intended recipient of  
this message you must not disseminate, copy or take any action in  
reliance on it. The sender takes no responsibility for the effect of  
this message upon the recipient's computer system.

View raw message