[EMAIL PROTECTED] wrote:
I don't think 2.3 is anytime too soon. I do think that the Turbine2.3 will be released in 2003 ;-)
developers learned from T2.2 that keeping something in beta for a year leads
to unhappy users, and a nightmare job on doing the release. The release of
T2.2 was a herculean effort (mostly because of decoupling large amounts of
functionality).
Having said that, 2.3 will release much sooner, but I don't have a great
feeling on when.
it will be a cleanup release (all stuff deprecated in 2.2 will be removed, cleanup configuration and logging, ...)
i think it will be releases within the next 6 month ...
we are also planning 2.2.x bugfix releases
martin
I will cc this to the turbine dev list...
One other thing I noticed.. The jetspeed StringUtils looks very much like
the StringUtils in commons-lang.. Turbine donated a lot of the code in
commons-lang, and maybe switching to that would simplify imports. I notied
some duplication like replace functions.. When I get back from holidays I
would be happy to integrate the commoons StringUtils into Jetspeed...
Eric
-----Original Message-----
From: Mark Orciuch [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 1:26 PM
To: Jetspeed Developers List
Subject: RE: DO NOT REPLY [Bug 15214] - Cleanup Logging
Nice timing! One interesting thing though: commons logging is supposed to
allow to plug in a logging framework of your choice. Default is log4j if
it's found on the classpath. AFAIK, Velocity and Torque are "hardwired" to
log4j so log4j will always be in the classpath and you wouldn't be able to
use, say JDK 1.4 logging. Correct me if I'm wrong about this.
BTW: Do you know when Turbine 2.3 will be released?
Best regards,
Mark Orciuch - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 11:01 AM
To: [EMAIL PROTECTED]
Subject: RE: DO NOT REPLY [Bug 15214] - Cleanup Logging
I have been watching the Turbine dev thread, and it seems that this same
thing has happened in T2.3 dev.. Henning removed all the Turbine Logging
stuff in favor of log4j... Just something to look at.
Eric
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 12:05 PM
To: [EMAIL PROTECTED]
Subject: DO NOT REPLY [Bug 15214] - Cleanup Logging
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15214>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15214
Cleanup Logging
------- Additional Comments From [EMAIL PROTECTED] 2002-12-23 17:04
-------
I think that step one to achieve what Raphael is proposing is to
provide a
replacement for Turbine Logging Service. This service makes it
difficult to
configure log4j loggers and its properties are confusing to say
the least. I
propose implementing our own logging service based on commons logging. We
would
continue using Turbine Log wrapper so no global coding change would be
required.
Since log4j is the default framework for commons logging, we
would provide a
default log4j.properties file and allow the users to fine tune logging to
their
liking. Any comments?
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
