On 6/13/06, Ted Husted <[EMAIL PROTECTED]> wrote:
On 6/12/06, Don Brown <[EMAIL PROTECTED]> wrote: > Please let us know your thoughts so we can focus on developing tools > to make migration as easy as possible. Thanks, My first thought would be how would migrating one part without the others would serve any practical purpose? My second thought would be how often would production-applications actually be migrated? In the field, it seems like that once a Struts application hits production, it continues to use the same version. A new application might use 1.2, but the old ones continue to plug along on 1.1. If it ain't broke, why fix it?
Why support multiple versions of struts code bases in production when you could use (and support) just one? I know we have apps that are in production that have 'migrated' from 1.0 though 1.1 to 1.2. I'd rather not support both sets for a large code base. -Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris
