struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dion Gillard" <dion.gill...@gmail.com>
Subject Re: Poll: What part of a Struts will be the most important to support for migration?
Date Mon, 12 Jun 2006 22:59:35 GMT
On 6/13/06, Ted Husted <ted.husted@gmail.com> wrote:
>
> On 6/12/06, Don Brown <donald.brown@gmail.com> 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: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>


-- 
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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message