I'm all for it actually. This way other container efforts can use our components without having dependencies on AF. This makes component reuse more socially acceptable.
Alex On Sat, 2004-08-07 at 01:26, Niclas Hedhman wrote: > On Saturday 07 August 2004 07:52, Paul Hammant wrote: > > I'm trying to submit some patches for Cornerstone to allow it (or at > > least ConnectionManager) to be used without Avalon. Specifically, in a > > Constructor Dependency Injection (CDI) manner. > > > > I'm having problems getting Maven 1.0 to compile it. Some custom Avalon > > goal is missing (see below) > > > > Any ideas? > > I hope you have managed to get Magic working by now. :o) > Shouldn't be that hard. > > > 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... > > > Cheers > Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
