SLING-12312 add jakarta.servlet support in RequestLocaleResolve

[enapps-enorman]

provide a variant of the RequestLocaleResolver#resolveLocale call that accepts a jakarta.servlet.http.HttpServletRequest for use cases that have migrated to EE9 or later.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[rombert]

This way the package has a dependency on both javax.servlet and jakarta.servlet and will not work for older environments. Was that the intention?

[enapps-enorman]

This way the package has a dependency on both javax.servlet and jakarta.servlet and will not work for older environments. Was that the intention?

I would prefer to get rid of the javax.servlet (EE8) but that is not possible yet so both have to be there for now.

Community support for all the versions of jetty that don't support EE9 or later have been eol for a while now.

I guess I don't expect that people who don't upgrade anything and keep using eol software should get to decide what can be changed. Progress requires moving forward.

org.apache.felix.http.jetty 5.x and org.apache.felix.http.jetty12 1.x both support servlets using either javax.servlet or jakarta.servlet

Why can't the EE8 loyalists just stay on the old version of org.apache.sling.i18n?

[rombert]

Why can't the EE8 loyalists just stay on the old version of org.apache.sling.i18n?

I don't think "loyalists" is the right term here. And we don't typically get to chose how our users manage their deployments. I'll start a dev@sling thread on this, I think it's important to have a clear policy.

Edit: https://lists.apache.org/thread/l9vghkdgr3ddtc703drs38506oswlod8

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud