On 10/29/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 10/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 10/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
We have a jul Logger and a JCL log in oasv.CommonsValidator
We're still using JCL elsewhere, so unless there is an
all-encompassing change, I'd recommend we lose the jul Logger.
Objections?
snip/
Switched to JCL before I forget this.
+1 for now ... but there's an outstanding ticket to switch all of Shale to
j.u.l at some point that we should talk about sometime on the dev list.
snip/
Thats a good option IMO for 1.4+ projects, but given that we've a
number of deps that use JCL it may buy us little ATM, and possibly
complicate the logging configuration.
As a concrete example, if we remove the JCL dep from
shale-dialog-scxml, there still is that runtime dep due to Commons
SCXML. We can go one step ahead and take care of it in Commons SCXML
(I had given it some thought prior to v0.5), but we're in turn bound
by Commons Digester. So.
I think it is generally accepted that any current web application
framework will end up having JCL on classpath, one way or the other.
-Rahul
-Rahul
Craig
-Rahul
