All modern application servers and runtimes include javax.* packages themselves. So, if you upgrade to Jakarta EE 8 compatible server or runtime you should have no issues However, if you elect using Jakarta EE 9.1 or greater, it uses jakarta.* packages. Most runtimes and servers have built-in transformer to run older javax.* compatible packages including shiro-web at runtime so you should have no issues.
> On May 10, 2022, at 7:36 AM, De Luise, Massimiliano > <[email protected] > <mailto:[email protected]>> wrote: > > Hi all! > I’m writing this email in order to check if shiro-web is compliant with jdk > 11+, specifically with jakarta library since javax library is removed. > > It seems to me that shiro-web still uses the javax.servlet library. > In fact: looking at the pom.xml of the last available version in maven > central (available at > https://repo1.maven.org/maven2/org/apache/shiro/shiro-web/1.9.0/shiro-web-1.9.0.pom > > <https://repo1.maven.org/maven2/org/apache/shiro/shiro-web/1.9.0/shiro-web-1.9.0.pom>), > or taking a look at the pom.xml of the github repository > (https://github.com/apache/shiro/blob/main/pom.xml > <https://github.com/apache/shiro/blob/main/pom.xml>), it can be seen the > javax.servlet dependency and not the jakarta.servlet. > > Can you please provide me some info about this? > Best regard, > Massimiliano De Luise
