commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@gmail.com>
Subject Re: [logging] log4j TRACE support justifies minor release
Date Thu, 16 Mar 2006 10:25:27 GMT
Its not an "official" release yet - just a release candidate - so its
only announced on the mailing list:

http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg76921.html

Niall

On 3/16/06, Remko Popma <remko@daiwasmbc.co.jp> wrote:
> PS.
> Can you point me to the URL of that announcement?
> I could not find it in
>  - the jakarta homepage news section
>  - the jakarta commons logging home page
>  - the wiki...
>
> Thanks, --Remko
>
> -----Original Message-----
> From: Dennis Lundberg [mailto:dennisl@apache.org]
> To: Jakarta Commons Users List
>
>
> Hello
>
> Commons Logging 1.1.0 is currently at release candidate 6, which was
> announced yesterday. A quote from that announcement:
>  "No major issues have been found in the last 5 candidates.
>  It is believed that release candidate 6 is ready for a full release."
>
> So it should be available real soon now ;-)
>
> --
> Dennis Lundberg
>
> Remko Popma wrote:
> > I hope this is the correct mailing list, apologies if dev would have been
> > better.
> >
> > Support for TRACE-level logging has been available for about eight months
> > now (log4j 1.2.12 was released in August 2005).
> > As you are probably aware, the current commons.logging release (1.0.4)
> > outputs Log.trace() calls at DEBUG level, even if the underlying log4j
> > version supports the TRACE level.
> >
> > I understand that this will be fixed in the upcoming JCL 1.1 release, but
> > this release will also include many other features and fixes, and the
> > Release Plan wiki page
> > (http://wiki.apache.org/jakarta-commons/Logging/1.1.0ReleasePlan)
> > does not have a release date and shows the status as "Preparations for
> > Alpha 1".
> > This sounds like a release is still a long time (several months) away.
> >
> > I also saw that plans for a 1.0.5 release (with support for log4j TRACE
> > level logging) were cancelled because developers wanted to include so many
> > new features that a 1.1 release was justified.
> >
> > I think it is great that developers are so enthusiastic and have many
> > ideas about how to improve JCL. For servlet-related work, the JCL 1.1
> > release is probably a great step forward. However, there must be many
> > developers working on both servlet and non-servlet projects who would
> > *really* like to have proper TRACE support in commons.logging soon, and
> > who don't like to wait for the JCL 1.1 release.
> > Please don't become like log4j 1.3, which has a zillion great features and
> > will be released Real Soon Now...
> >
> > I believe that TRACE support alone would justify a minor release.
> > Would it be a lot of work to release a new version of commons.logging
> > (1.0.5) with *only* the TRACE issue fixed, and no other changes?
> >
> > Respectfully,
> > --Remko Popma
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>

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


Mime
View raw message