1) I'd like my name kept out of subject lines please. > I therefore propose the following: Phoenix drops the "Avalon > reference container" part of itself and joins Merlin, Fortress > and the others as just another container.
+1 It is one container in a multi-container world. > In my opinion, a reference container is what you go look at > to get clarification of a contract in framework. Not something > you'd deploy commercially. My opinion too. Tweety is closer. I'll say again that it should be part of jakarta-avalon-framework CVS. > ... Then, once there are features in those containers that > have withstood the tests of real-life deployment, should the > features be merged back into framework and the reference > container. I disagree. We should keep the ref very light. I buy the idea of "not intended for real deployments". - Paul __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
