Here is a prime example of someone using an alpha product whichs explicitly stated "the developer team is not investing _any_ effort in providing back compatibility between alpha releases". And when it changes they are ... what ... shocked? If they are, then they shows a decided lack of intelligence.
At 12:19 PM 5/20/01 -0700, Jon Stevens wrote: >Here is a prime example of why deprecation is important. > >-jon > >------ Forwarded Message >From: steve <[EMAIL PROTECTED]> >Reply-To: [email protected] >Date: Sun, 20 May 2001 12:29:52 -0400 (EDT) >To: [email protected] >Subject: Velocity and Avalon > >Hi, > >I'm trying to use Avalon with Velocity and I've >run into a version conflict in the logger. > >I have Avalon 4.0b1 ... > >I see that Velocity uses the Avalon logger by >default and I haven't changed that, but it looks >like it must be an older version. Can I simply >replace the logger in Velocity with the newer >version? ...any other tips? > >Thanks, > >Steve > >PS: I had sent a "newbie" question out last week >about suggestions on the best way to integrate >a DB component into a Velocity servlet. I looked >at Turbine but in the end decided that it didn't >really suit my needs. I did discover that Avalon >would provide me with some very useful >components. Thanks to all who responded. > > >------ End of Forwarded Message > > Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
