Create rules for upgrading web server if necessary
Opened this issue · 3 comments
According to the migration guide:
Due to the Jakarta EE migration, make sure to upgrade to Tomcat 10, Jetty 11, or Undertow 2.2.19 with the undertow-servlet-jakarta artifact, alongside switching your javax.servlet imports to jakarta.servlet (Jakarta EE 9). For the latest server generations, consider Tomcat 10.1 and Undertow 2.3 (Jakarta EE 10).
Investigate and create rules if necessary.
In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.
This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.
Detection of Tomcat, Jetty, or Undertow usage below the given versions. Also, migration to Jakarta. Migration of the versions of the specific web servers would have to be investigated
Downgrading priority - in principle, web server usage is transparent in Spring Framework, so there is no way to detect which one is being used.