logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Opaczewski, Greg" <GOpaczew...@orbitz.com>
Subject RE: log4j 1.2.15
Date Wed, 21 Feb 2007 15:43:13 GMT
That's correct, I was asking about the 1.2.15 release.  Can you provide
an ETA for this?  I'm just trying to gauge whether I can wait for the
official release.

thanks-
Greg

> -----Original Message-----
> From: Curt Arnold [mailto:carnold@apache.org]
> Sent: Wednesday, February 21, 2007 1:45 AM
> To: Log4J Developers List
> Subject: Re: log4j 1.2.15
> 
> 
> On Feb 20, 2007, at 10:32 PM, Opaczewski, Greg wrote:
> 
> > Is it possible to get a 1.2.15 sometime soon?  We have some
> > performance issues that have recently become critical that may be
> > solved by a switch to async logging, but I was waiting on a patch
> > for this issue first:
> >
> >
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=41186
> >
> >
> 
> I'm interpreting that you meant that you are waiting on a release
> with the patch for that issue.  The issue itself has been fixed in
> the SVN which you acknowledged in your comment on the issue.  If the
> patch didn't fix the problem, please reopen the bug.
> 
> I've added a few additional dependencies to the 1.2.15 release bug
> (40951).  If anyone has a favorite bug that should go into 1.2.15,
> please mention it or add it as a dependency on the bug.
> 
> I've been looking at the bugs around ThrowableInformation.  I'm torn
> whether to:
> 
> a) Eliminate the existing VectorWriter class and pass a PrintWriter
> wrapping a StringWriter, then break the StringBuffer at line
> separator boundaries.
> 
> b) Replace NullWriter with StringWriter and check if anything got
> handed off to the StringWriter on all the overloaded print calls.
> 
> The first approach would do the right thing if you had a
> printStackTrace that did use a lot of the unsupported methods or the
> print() methods.  However, it would be a radically different code
> path.  The second would have the same code path as long as you used
> the supported methods but would have ugly behavior if you did use
> PrintWriter.write(int) a lot (each character as a separate String in
> the array).  Still writing test cases around ThrowableInformation to
> capture the current behavior at the moment.
> 
> Applying the updated ASF Source and Copyright Policy is required in
> any new release.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org


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


Mime
View raw message