On Tue, 12 Nov 2002 19:40, Nicola Ken Barozzi wrote: > 2) we keep only *one* set of utility classes called avalon-util > (no more fancy names, pleeease)
The initial name for this was AUT (Avalon Utility Toolkit). However we dropped that idea as we needed to get a stable release out for cocoon. We could revive that but I am not sure it is a great idea. Either way I would -1 any backwards incompatible changes to anything released as 100% stable (in particular framework/logkit) even though from a technical perspective it would be nice ;). > > Avalon Phoenix: establishes the server, rules, and > > contracts for hosting server applications. > > This is a very delicate point. > > Phoenix is big, really big. IMV it's at the same level of Avalon, and > should be a project in its own right. > > I dunno, what do the Phoenix guys think that should be done, given that > we should unite? -1 for the same reasons I have already explained to you when you asked me last time ;) -- Cheers, Peter Donald -------------------------------------------------- Logic: The art of being wrong with confidence... -------------------------------------------------- -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
