Migrate from EE 8 to EE 9

[basil]

No description provided.

[mPokornyETM]

Sorry guys, but migth somebody explaint to me why we need this changes? There is no issue linked, no explenation (PR description)

[MarkEWaite]

Sorry guys, but might somebody explain to me why we need this changes? There is no issue linked, no explanation

Sure! Thanks for asking. The upgrade from Jenkins 2.462.3 to Jenkins 2.479.1 includes:

• Spring Security 5 upgraded to Spring Security 6
• Java EE 8 upgraded to Jakarta EE 9
• Eclipse Jetty 10 upgraded to Eclipse Jetty 12
• Java 11 required minimum Java version upgraded to Java 17 minimum required Java version

Those upgrades add new classes and new methods. A compatibility layer was added in Jenkins core in order to retain compatibility with the prior implementations while using the new classes and methods. That compatibility layer is a large body of code that we want to eventually remove (as much as we can). In order to remove that compatibility layer, plugins need to be updated to use the new classes and methods instead of using the compatibility layer.

Prior releases of the lockable resources plugin worked as expected on Jenkins 2.479.1 because they relied on the compatibility layer in Jenkins 2.479.1. This pull request adapts the plugin to use the new methods and new classes rather than relying on the compatibility layer. Similar changes will be needed in all Jenkins plugins that rely on the compatibility layer.

The key goal of this pull request is to complete the Spring Security 6.x upgrade project in the source code of the lockable resources plugin. The change switches from:

• deprecated StaplerRequest to StaplerRequest2
• deprecated StaplerResponse to StaplerResponse2
• javax.servlet.ServletException to jakarta.servlet.ServletException

This pull request is one of many that have been submitted to complete the Spring Security 6 upgrade one plugin at a time. Many more pull requests will be submitted like this one over the next 6-9 months.

[mPokornyETM]

Similar changes will be needed in all Jenkins plugins that rely on the compatibility layer.

thats a huge effort. I wihs you all many luck. You will need it.