enapps-enorman commented on PR #13: URL: https://github.com/apache/sling-org-apache-sling-i18n/pull/13#issuecomment-2099146151
> 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](https://endoflife.date/eclipse-jetty) 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? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
