I'm concerned it will do more harm than good. With the release of Struts 6.7 we have a decent upgrade path as most Actions/Interceptors/Results can now be made forwards compatible with 7.0. It leaves limited additional work when upgrading to 7.0. By renaming the packages again we'd be breaking that path.
Also, getting Struts 6 running alongside 7 will be no easy feat, assuming it's even possible. The effort of doing this would only make sense if it were notably less than the effort to actually migrate code from Struts 6.7 to 7.0. I agree it would make sense to drop the '2' from org.apache.struts2 but if the benefit is only really aesthetic then I'm not sure it's worth the cost (significant upgrade friction). On Mon, Nov 18, 2024 at 3:11 AM Lukasz Lenart <lukaszlen...@apache.org> wrote: > > niedz., 17 lis 2024 o 12:00 Kusal Kithul-Godage > <kusal.kithulgod...@gmail.com> napisał(a): > > > > Curious what the use case for having both Struts 6 and 7 in the same > > WAR would be? > > In some cases you must rewrite part of your actions and this might > help by running two versions of the framework in parallel. It's one of > the strategies for migrating Struts 1 into Struts 2. > Also I would like to do something with "struts2" as this can be > misleading. Maybe reverting back to "org.apache.struts" is an option. > > > Cheers > -- > Łukasz > > --------------------------------------------------------------------- > 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
