I already added Spring 7 support in
https://github.com/apache/struts/pull/1233 - but as a separate Maven
profile, which runs as a separate job in our builds.

This ensures we maintain backwards compatibility with Jakarta EE 10 /
Spring 6 whilst also supporting Jakarta EE 11 / Spring 7 (we are still
missing Tomcat 11 support though). We should however bump the version
properties in that Maven profile as it's still using older milestones.

The idea here was, that when we decide to officially drop support for
Jakarta EE 10 / Spring 6 (Struts 8.0?) we can merge that Maven profile
into the default POM configuration. But until then, we should have
build coverage for both.


On Sun, 14 Dec 2025 at 01:18, Lukasz Lenart <[email protected]> wrote:
>
> Looks like we are good to upgrade to Spring 7, at least it's a good
> idea for Struts 7 - in both cases we are going to support JakartaEE,
> any objections?
>
> https://github.com/apache/struts/pull/1467
>
>
> Cheers
> Ɓukasz
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to