The Velocity 1.5 update was painless. It requires the latest Commons Collection, which is also required by Torque 3.1/3.2.
I had more issues upgrading from Turbine 2.2 to Turbine 2.3, though perhaps that's my fault for revising my app to not need deprecated features. (and hitting a few unexpected snags). Also had a problem with new escaping features in the Configuration library causing my properties file not to be read. I initialize Torque 3.2 with the Avalon component service. Actually, the old component service works with Torque 3.1 but not with Torque 3.2. (meant to file a bug report on this, but see I never did). WILL On 4/30/07, Scott Eade <[EMAIL PROTECTED]> wrote:
I knew that would get Henning and Wills' attention. I am wondering if for 2.3.3 we should update some of our dependencies. I know Will updated his apps to use Velocity 1.5 - where there any changes required for this (to turbine or your app)? Torque also springs to mind - we could at least go to 3.2 (hmm, does Torque 3.2 work with ACSYaafiComponentService or do I need to add a comment that trunk/3.3 is required?) Thomas has already taken care of commons-fileupload, but there may be a couple more that can also be dropped in. Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
