Hi, In https://github.com/apache/sling-org-apache-sling-i18n/pull/13 a discussion was started regarding javax.servlet / jakarta.servlet support.
The PR as it is requires both packages to resolve ( javax.servlet / jakarta.servlet ), which means users that only have javax.servlet support would be unable to consume newer versions of the i18n bundle. We have typically tried very hard to keep backwards compatibility so that our bundles are drop-in replacements; we don't do maintenance branches for older versions because it would be a burden to us. Of course, we can always revisit that. So my question is - where do we stand on the jakarta.servlet / javax.servlet topic? It's either a) we drop support for javax.servlet and require jakarta.servlet or b) we keep supporting javax.servlet, using newer features of jakarta.servlet without a hard binding, where applicable. Thoughts? Thanks, Robert
