Bump Tomcat && Jetty && Spring Boot

[tesshucom]

Prerequisites: #2305

Problem description

A major version upgrade of Jetty will be done in v111.3.0. #838 On the other hand, Tomcat will maintain the status quo.

---

The comparison of each product version is as follows. The impact of Jakarta EE 9 is great, but now it is just before that. We need to keep an eye on new information.

Jpsonic	Jetty	Tomcat	Servlet	EE / Spring Boot	Namespace
111.2.0	9.4.x	9.0.x	3.1	Java EE 7 / 2.x	javax.servlet	8 and later
111.3.0	10.x	9.0.x	4	Jakarta EE 8 / 2.x	javax.servlet	11 and later
?	11.x	10.0.x	5	Jakarta EE 9 / 3	jakarta.servlet
?	12.x?	10.1.x	6	Jakarta EE 10

Additional notes

• Preparing for Spring Boot 3.0
  • Upgrade to Java 17 ✅
  • Upgrade to the Latest Spring Boot 2.7.x ✅
  • Check for Calls to Deprecated Code. All deprecated code will be removed. ❗
  • PathPatternParser (Recommendation) 😗
  • Check if Third-party Projects Have Jakarta EE 9 Compatible Releases 😟
    • Tomcat and Jetty should be upgraded at the same time
    • Upgrading Tomcat 10.0.x
    • DWR with tomcat 10 directwebremoting/dwr#39
    • DWR with Java 11 : Can't start embedded Jetty #1630
      • It can be avoided by downgrading to DWR 3.0.0-rc3-RELEASE and seems to work with Java17. Worst case, there will be a way to not upgrade DWR until Java 11 is EOL. Premier Support of Java 11 by Oracle Expires September 2023
  • Try the Spring Boot Milestones 😑

    • Although we don’t recommend it for production, you can try Spring Boot 3.0 milestones today to see how hard it will be to migrate your project.

---

There are some barriers to resolving this issue. However, there is a grace period until it is completely resolved.

Spring Boot 2.7 is the last planned release in the 2.x line. We’ve extended our open source support for this release by an additional 6 months until November 2023.
In addition, commercial support for Spring Boot 2.7 has also been extended and is available until February 2025.

[tesshucom]

It is probably expected that it will be inserted between the currently planned v111.3 and v111.4.

[tesshucom]

Although the details were unclear when this issue was published, the target versions are expected to be:

Jpsonic	Jetty	Tomcat	Servlet Spec	Spring Boot	Namespace
v114	12.0.x	10.1.x	6	3.2	jakarta.servlet

• Apache Tomcat Versions
• Eclipse Jetty Versions

It's true that Spring Boot 2.7 is reaching its expiration date. However, since Jpsonic supports multiple containers, it is necessary to take into account the Servlet Spec, App Server's Servlet Versions, and Spring's App Server compatibility status.

The most realistic option right now is to jump from Spring Boot 2.7 to 3.2. This will enable both Jetty/Tomcat to use Sevlet6.