> > This > > is exactly what I was referring to above about stripping out features > and > > making it pluggable. We can do it. > > Dependency management, lifecycles, etc -- it should all be "pluggable." > In > fact, I'd like to see us get to the point that our components don't _have_ > to implement anything from Avalon framework. So that just about > everything > is optional, with of course, some things being "recommended."
+1000 if I could. POJO components would then become a reality. > > 1). Make a list of these seperable features/aspects > > 2). Order wrt complexity of achieving separation > > 3). Adjust order with respect to possible dependencies > > 4). Take top most feature or setup goals and start re-factoring Merlin > to > > make the feature pluggable and isolated. > > 5). Go to 4 until list is gone > > > > At the end of the day Merlin will be what we want it to be. > > +1 Yes Merlin is the future but how he matures is in all of our hands. > I'd like to point out though, that I feel most of these issues are > _implementation_ issues and can be sorted out fairly easily I hope. If > someone strongly feels they _can't_ be, then that should be voiced. +1 > The more important issue is that we're all working together on a common > solution rather than split across several incompatible container > implementations. I think we are coming to that consensus. Yes yes yes! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
