If it breaks backwards-compatibility, I'd suggest not doing it. I've always been impressed with projects like Spring that've maintained backwards compatibility w/o making a breaking change such as this.
On Nov 27, 2012, at 3:54 PM, Jeff Black <jeffrey.bl...@yahoo.com> wrote: > Never mind. > > I suppose it makes sense to some extent; however I'm with Dave when it comes > to incorporating the version number in the package name. > > Just my two cents. > > > > ________________________________ > From: Jeff Black <jeffrey.bl...@yahoo.com> > To: Struts Developers List <dev@struts.apache.org> > Sent: Tuesday, November 27, 2012 4:50 PM > Subject: Re: Plan for Struts 3 > > Is it really necessary to alter the package name? > > > > ________________________________ > From: Lukasz Lenart <lukaszlen...@apache.org> > To: Struts Developers List <dev@struts.apache.org> > Sent: Thursday, November 22, 2012 5:35 AM > Subject: Re: Plan for Struts 3 > > 2012/11/22 Dave Newton <davelnew...@gmail.com>: >> How useful is the Struts 1 plugin? > > It's mentioned as a migration way for S1 projects, but we can drop > support for S1 in S3 > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
