On 8/31/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > Depends on the size of your project, the features you've used and how you've > developed it. The following notes should help you assess it yourself: > > Notes on upgrading from 1.1 to 1.2.4: > http://wiki.apache.org/struts/StrutsUpgradeNotes11to124 > > Notes on upgrading from 1.2.4 to 1.2.7: > http://wiki.apache.org/struts/StrutsUpgradeNotes124to127
And, most importantly, how many deprecated features a team is using. We do retain backward compatability between 1.x releases. So, if we did our job right, and if a1.1 release compiles *without* deprecation warnings, then it should be compile-and-go for 1.2, with zero code changes. Again, if the 1.1 compiles *without* deprecation warnings. Ditto for 1.2. If a 1.2 application compiles *without* deprecation warnings, then it should be compile-and-go for 1.3. (And if it isn't, we want to hear about it!) But, if an application already has deprecation warnings for 1.1 and a team waits for 1.3, then there will be that much more work to do. Of course, the real fun is taking advantage of the new features, like wildcard mappings and lazy validator forms in 1.2, and the very cool "extends" that's coming in 1.3. -- HTH, Ted. http://www.husted.com/poe/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
