Re: log4cxx 0.10.1 release plan (Re: link error in release mode with Visual Studio 2008 on log4cxx-user)

[Dale King <da...@gmail.com>]

I appreciate your work on this, but the thing that desperately needs a new
release is Chainsaw! It has been over 4 years since it has been released.
The current release is based on the abandoned 1.3 branch of Log4J so there
are several things that do not work with the current versions of Log4J and
Log4Cxx.

On Wed, May 12, 2010 at 12:39 AM, Curt Arnold <ca...@apache.org> wrote:

> Cross posting on log4cxx-user since the question was asked there.  Followup
> discussion should be on log4cxx-dev.
>
> Begin forwarded message:
>
> > From: Curt Arnold <ca...@apache.org>
> > Date: May 11, 2010 11:38:19 PM CDT
> > To: Log4CXX Dev <lo...@logging.apache.org>
> > Subject: log4cxx 0.10.1 release plan (Re: link error in release mode with
> Visual Studio 2008 on log4cxx-user)
> >
> >
> > On May 10, 2010, at 8:44 AM, Reynolds, John wrote:
> >
> >> Good to see you back Curt. Any dates on next release?
> >>
> >> I meant what executable format ( looked it up, it is Mach-O ). I knew it
> wasn't ELF even though it does use the FreeBSD tools.
> >>
> >
> > I've just logged http://issues.apache.org/jira/browse/LOGCXX-363 for a
> subsequent release.  If there are bugs that really should be addressed
> before a release, mark it as a blocker on LOGCXX-363.  If there are any bugs
> that you believe that you think are ready to go, please mention them on the
> list.   Making VS 2010 happy would be one of them.
> >
> > I had really good intentions to work a log4cxx release as soon as I got
> through log4j 1.2.16, but that took much longer than I expected and there
> are still some aftermath issues that need to be cleaned up.
> >
> > Any help on prioritizing or checking the bug reports would be
> appreciated.
> >
>
>


-- 
Dale King

Re: log4cxx 0.10.1 release plan (Re: link error in release mode with Visual Studio 2008 on log4cxx-user)

[Scott Deboy <sc...@gmail.com>]

A new Chainsaw release with a lot of new features will be released in  
the near future. You can pull the source down and build with maven if  
you'd like to try it today.

Annotated logs, multirow events, highlighting of search matches in the  
table, better multicast Dns support and more. See the chainsaw release  
notes in the help menu for a list of everything.

Scott

On May 12, 2010, at 8:07 AM, Dale King <da...@gmail.com> wrote:

> I appreciate your work on this, but the thing that desperately needs  
> a new release is Chainsaw! It has been over 4 years since it has  
> been released. The current release is based on the abandoned 1.3  
> branch of Log4J so there are several things that do not work with  
> the current versions of Log4J and Log4Cxx.
>
> On Wed, May 12, 2010 at 12:39 AM, Curt Arnold <ca...@apache.org>  
> wrote:
> Cross posting on log4cxx-user since the question was asked there.   
> Followup discussion should be on log4cxx-dev.
>
> Begin forwarded message:
>
> > From: Curt Arnold <ca...@apache.org>
> > Date: May 11, 2010 11:38:19 PM CDT
> > To: Log4CXX Dev <lo...@logging.apache.org>
> > Subject: log4cxx 0.10.1 release plan (Re: link error in release  
> mode with Visual Studio 2008 on log4cxx-user)
> >
> >
> > On May 10, 2010, at 8:44 AM, Reynolds, John wrote:
> >
> >> Good to see you back Curt. Any dates on next release?
> >>
> >> I meant what executable format ( looked it up, it is Mach-O ). I  
> knew it wasn't ELF even though it does use the FreeBSD tools.
> >>
> >
> > I've just logged http://issues.apache.org/jira/browse/LOGCXX-363  
> for a subsequent release.  If there are bugs that really should be  
> addressed before a release, mark it as a blocker on LOGCXX-363.  If  
> there are any bugs that you believe that you think are ready to go,  
> please mention them on the list.   Making VS 2010 happy would be one  
> of them.
> >
> > I had really good intentions to work a log4cxx release as soon as  
> I got through log4j 1.2.16, but that took much longer than I  
> expected and there are still some aftermath issues that need to be  
> cleaned up.
> >
> > Any help on prioritizing or checking the bug reports would be  
> appreciated.
> >
>
>
>
>
> -- 
> Dale King
>