You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jakarta EE 9 is out already along with stable versions of the two most popular containers - Tomcat 10 and Jetty 11. shiro-jersey internally still uses javax (e.g. import javax.ws.rs.core.Response in ShiroExceptionMapper) so it is incompatible with an application that runs on these two containers. It would be nice to release a new version that is compatible with them. Unfortunately a single version cannot be made compatible with both the "old" javax and the "new" jakarta namespaces so perhaps a new major version should be released.
The migration is simple enough - just depend on the new artifact versions and rename the imports from javax.* to jakarta.*.
Jakarta EE 9 is out already along with stable versions of the two most popular containers - Tomcat 10 and Jetty 11.
shiro-jersey
internally still usesjavax
(e.g.import javax.ws.rs.core.Response
inShiroExceptionMapper
) so it is incompatible with an application that runs on these two containers. It would be nice to release a new version that is compatible with them. Unfortunately a single version cannot be made compatible with both the "old"javax
and the "new"jakarta
namespaces so perhaps a new major version should be released.The migration is simple enough - just depend on the new artifact versions and rename the imports from
javax.*
tojakarta.*
.cc @silb
The text was updated successfully, but these errors were encountered: