> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Eike Stepper > Sent: Wednesday, June 23, 2004 4:43 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [PROPOSAL] The Future of Avalon Repository > > hi niclas, > > the "avalon must die" link you provided is a bit scaring! > > after several weeks of struggling with ~500 classes > and an unconsolidated documentation it really doesn't > light my mood that i have to read that all my effort was > for a potentially starving technology ;-( > > could you please explain the dilemma for an unexperienced > "external" like me?!
The dilemma is now, thankfully, past us. Or at least that is my opinion now. For the new site (which is not yet published) I put together a little summary of Avalon's history which includes an explanation of why Avalon was in a bit of a bind for such a long time. Much of it was based on some earlier documentation I wrote about the various containers: http://wiki.apache.org/avalon/ContainerStory Long story short is that now that Excalibur has been promoted to a new Apache project (http://excalibur.apache.org) and Phoenix has a home with the new Loom development at Codehaus (http://loom.codehaus.org) a lot of controversy can be averted. Avalon has things in order and can focus on a (newer) single container platform, ie- Merlin, while users of the older Avalon technologies aren't left high and dry. So, I for one believe our most difficult days are behind us and users and developers alike have no more need to worry about Avalon's status. J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
