1) We strive for a lowest common denominator (LCD) approach with embracing of multiple value-added implementation, which may end up divergent without that being considered a failure. Thus A-F's Java interfaces are our point of unification. There is no single container. There is no unified assembly or configuration meta info specification at the application level. XML and other.
2) We drop a unified component-level meta info dependancy and configuration design. XML and other.
This has been discussed to the tune of a million characters. Let us just see which of the two above committers have moved on (or not).
At some risk, I'd like to reopen this then. Proposal :
With all do respect, Paul, if we do this, then our job is done. THe Avalon CVS is all that we should keep and everything else goes by-by.
The fun stuff would all be done elsewhere.
Merlin, Fortress and others are still here. There is still work to make components (seems to heve been forgotten). I am a late arriver to XP. Though I am lucky enough to work for one of the worlds most practiced XP shops. More than ever I believe that we Avaloners are too design-ahead-of-need focussed. Woods for trees - declare A-F complete at the Java level and stop talking about Avalon 5 etc. Embrace the multi container view and start componentizing the rest of Apache.
OSS is not awlays about fun. We often miss off the point at which we should be claiming we are finished at API level and merely work on improved and alternate implementations.
I fail to get excited about this proposal. Maybe it's just me. I gave your proposal some more visibility to see if it is just me.
Grand. I firmly in what I said as the best way for peace to break out here.
- Paul
-- http://www.thoughtworks.com -> The art of heavy lifting. Home for many Agile practicing, Open Source activists...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
