Within the 1.x series, we've made each subsequent release backwardly-compatible with the last, but only with the last. With each release, some members were deprecated, and in the next release removed.
The most efficient approach might be to upgrade the binaries one release at a time. Recompile, note any deprecation warnings, and address the warnings until it builds clean, and then go onto the next. Depending on how the application was written, jumping ahead might work, but it might also be a frustrating exercise, since 1.3.5 isn't going to know about things we removed in 1.1. Better to take it one step at a time. If you don't have any UI tests on hand, I'd take this opportunity to create some. The Selenium package is quite good. * http://www.openqa.org/selenium/ You can quickly record a series of UI tests, and then play them back during the upgrade. -Ted. On 11/2/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
Struts 1.3.5 is the latest "ga" (or production ready) version of Struts - so thats probably you're best bet. http://struts.apache.org/downloads.html > Where can I read about the different between 1.0 and 1.35, I guess it's > a big step????? We have upgrade notes on the wiki. Unfortunately they only start at upgrading from Struts 1.1 - there isn't any from 1.0, but they will help you: http://wiki.apache.org/struts/StrutsUpgrade There are also the release notes, I'll point you to the latest - but there are links on each version of the release notes, back to the previous version. So you can navigate back through to Struts 1.0: http://struts.apache.org/1.x/userGuide/release-notes.html Niall
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
