Niclas Hedhman wrote: <snip/>
The main issue here revolves around the suggested changes, and I want to kick off a discussion of whether this is 'desirable'.
Gang, Paul's changes can probably best be summarized as;
1. Moving any 'functional' code into POJOs, and have an Avalon wrapper to maintain Avalon compatibility.
2. Introduction of the "No Logging Strategy" with a connection monitor, and monitor adapters for Avalon and Commons-logging.
We need to discuss if these are changes that are in line with the Avalon direction and a way that should be supported, maintained and encouraged.
Personally, I have no strong opinion at this point in time, and would like the folks to speak up. Preferably also the Excalibur camp...
I am (strongly) +1 on introducing the no-logging strategy, +1 on the Constructor Dependency Injection support in the components avalon produces,
provided everything remains backwards-compatible. Without having checked out the patches yet, I'm sure Paul knows what he's doing wrt backwards compat. Maybe a good idea to just give him back commit privs?
Oh, and sure, I'm also +1 on introducing this stuff @ excalibur. But its an orthogonal discussion as excalibur doesn't depend on cornerstone...
-LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
