You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-user@logging.apache.org by Bob Rossi <bo...@cox.net> on 2006/12/11 16:20:30 UTC

maturity

Hi,

I'm currently evaluating several logging libraries for use in a project.
I've played with log4cpp, and am now looking at log4cxx. Is log4cxx
mature? My general feeling from looking at the website is that the
project should not be used yet in stable software. This is because I've
noticed that the current release comes with a huge notice that it
shouldn't be used. However, no other releases have been posted. Is there
a reason for this?

If possible, I would appreciate feedback from users/developers letting
me know if they consider the current svn snapshot of log4cxx to be
mature enough to be incorporated into stable software. 

I'm already using apr. If log4cxx is considered stable, I'd like to use
it in the native mingw environment. Is this currently possible? I'm
using autotools. If it's not currently possible, and log4cxx is
considered mature, I could do some work to get the autotools stuff
correct. Although, I wouldn't be interested in maintaining it long term.

Thanks,
Bob Rossi

Re: maturity

Posted by Curt Arnold <ca...@houston.rr.com>.
On Dec 11, 2006, at 9:20 AM, Bob Rossi wrote:

> Hi,
>
> I'm currently evaluating several logging libraries for use in a  
> project.
> I've played with log4cpp, and am now looking at log4cxx. Is log4cxx
> mature? My general feeling from looking at the website is that the
> project should not be used yet in stable software. This is because  
> I've
> noticed that the current release comes with a huge notice that it
> shouldn't be used. However, no other releases have been posted. Is  
> there
> a reason for this?
>
> If possible, I would appreciate feedback from users/developers letting
> me know if they consider the current svn snapshot of log4cxx to be
> mature enough to be incorporated into stable software.
>
> I'm already using apr. If log4cxx is considered stable, I'd like to  
> use
> it in the native mingw environment. Is this currently possible? I'm
> using autotools. If it's not currently possible, and log4cxx is
> considered mature, I could do some work to get the autotools stuff
> correct. Although, I wouldn't be interested in maintaining it long  
> term.
>
> Thanks,
> Bob Rossi

The log4cxx 0.9.7 release was released before log4cxx was donated to  
Apache Software Foundation.  There has not be a subsequent release  
since it has been in the ASF, due to procedural and technical  
issues.  Most of the procedural issues have been resolved and there  
are a few outstanding technical issues that are listed as blocking a  
0.10.0 release (http://issues.apache.org/jira/browse/LOGCXX-62).   
Basically all it should require is a development sprint to get the  
issues knocked off and I'm hoping to use some time around Christmas  
to give everybody something under their tree.

log4cxx is not "stable" in the sense of the API's being frozen and  
guaranteed binary compatibility between versions.  However, many  
people have reported using svn snapshots in production environments.   
The topic comes up frequently enough that you should find discussion  
on it fairly easy by checking the mailing list archives, for example  
http://marc.theaimsgroup.com/?l=log4cxx-user&m=114546446721447&w=2.

I haven't checked MinGW for a while.  We have submitted changes back  
to APR regarding MinGW, but I haven't attempted to build there for a  
while.