The migration from javax.servlet to jakartaee.servlet has major implications on Jenkins. Even setting aside plugin compatibility, the migration implies the following upgrades to core and core components:
Upgrade Apache Commons FileUpload from 1.4 to 2.0 (first version that supports new Servlet API imports)
Upgrade Jakarta Server Pages (JSP) API from 2.3.3 to 3.0.0 (required for Jetty upgrade)
Upgrade Jakarta Servlet API from 3.1.0 to 5.0.0 (the main change)
Upgrade Jakarta Standard Tag Library (JSTL) API from 1.2.7 to 2.0.0 (required for Jetty upgrade)
Upgrade Jetty from 10.x to 11.x (first version that supports new Servlet API imports)
Upgrade Maven Shade Plugin from 3.3.0 to 3.3.1 (required for Java 17 upgrade)
Upgrade Spring Framework from 5.3.x to 6.0.x (first version that supports new Jakarta imports, requires Java 17)
Upgrade Spring Security from 5.7.x to 6.0.x (first version that supports new Jakarta imports, requires Java 17)
Upgrade WebSocket API from 1.1 to 2.0.0 (first version that supports new Jakarta imports)
In addition to the above, a plugin compatibility layer needs to be written to support plugins that consume the old javax.servlet API.
The migration from javax.servlet to jakartaee.servlet has major implications on Jenkins. Even setting aside plugin compatibility, the migration implies the following upgrades to core and core components:
In addition to the above, a plugin compatibility layer needs to be written to support plugins that consume the old javax.servlet API.
Originally reported by basil, imported from: Jakarta EE 9 migration