Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <434C3238.2040900@j-hohwiller.de>
Date: Tue, 11 Oct 2005 23:44:24 +0200
From: Joerg Hohwiller <joerg@j-hohwiller.de>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050817)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [logging] log4j 1.3 support
References: <43412BBF.5070607@j-hohwiller.de>
	 <433C4F81.3030009@j-hohwiller.de>
 <22547.1128079859@www15.gmx.net>	 <1128127763.3855.35.camel@localhost.localdomain>
	 <1128134571.3994.20.camel@localhost.localdomain>
	 <433F98FA.4070106@j-hohwiller.de>
	 <1128249202.6122.28.camel@localhost.localdomain>
	 <dhp4lm$vhp$1@sea.gmane.org>
 <43411360.30804@j-hohwiller.de>	 <43412BBF.5070607@j-hohwiller.de>
	 <5.2.1.1.0.20051009225104.03696f30@127.0.0.1>
 <1128936705.4437.8.camel@localhost.localdomain>
In-Reply-To: <1128936705.4437.8.camel@localhost.localdomain>
OpenPGP: id=60DCBFFF
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

Simon Kitching wrote:
> nb: top-posting, esp. in reply to a thread that already uses
> bottom-posting, makes an email *really* hard to read!
> 
> On Sun, 2005-10-09 at 22:59 -0500, Jacob Kjome wrote:
> 
>>Can the problem be restated?  Seems like this email catches the end of a 
>>conversation.  What is the issue at hand?
I am sorry for this. I wanted to have the issue raised on this list, but
very little time at the moment. Thanks to Simon for making this clear.
> 
> 
> 
> This bugzilla entry has some of the relevant history.
> http://issues.apache.org/bugzilla/show_bug.cgi?id=34437
> 
> This thread has more discussion:
> http://www.mail-archive.com/log4j-dev@logging.apache.org/msg04408.html
> 
> 
> 
>>As for TRACE, that is new to Log4j-1.2.12 and didn't exist in versions 
>>previous to it.  If it doesn't exist in a 1.3 alpha binary release yet, it 
>>will.  There are plans to get a new 1.3 alpha build out soon.  There's been 
>>a lot of work done in the source to make 1.3 more compatible with 1.2, 
>>which wasn't the plan early on in 1.3's development.  But now the thought 
>>is try to keep 1.3 as compatible with 1.2 as possible.  If you are worried 
>>that the current alpha is incompatible with the 1.2.xx branch, please try 
>>building Log4j-1.3 from source and then compile against that.  That will 
>>provide a much better test of JCL 1.2.xx and 1.3 compatibility.
> 
> 
> That's nice to hear.
I agree. I will let you know when I checked the latest 1.3 from HEAD.
> 
> Regards,
> 
> Simon
Take care
  J�rg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDTDI4mPuec2Dcv/8RAhyEAKCA6+UI8bnOxxel5VO1gDjKl3MNbgCfWoI1
D0lwKcJRlU+LfiGsjG3iMfo=
=EQ4z
-----END PGP SIGNATURE-----

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