[ 
https://issues.apache.org/jira/browse/SHIRO-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539523#comment-17539523
 ] 

Boris Petrov commented on SHIRO-803:
------------------------------------

Well, I haven't really tried but as far as I understand, this works by 
modifying the contents of a JAR/WAR, correct? If so, how do I use that in 
development? There I use something like Gretty to run an embedded Tomcat 
server. It would complicate the build-process very much. The same goes for the 
production build.

In any case, this tool is a temporary workaround. The "correct" solution would 
be for all libraries to provide a Jakarta version. Most have already (as it's 
been 1.5 years since the release). Shiro is one of the few left. So it would be 
nice to get a Jakarta-enabled version of Shiro too. :)

> Migrate to Jakarta APIs
> -----------------------
>
>                 Key: SHIRO-803
>                 URL: https://issues.apache.org/jira/browse/SHIRO-803
>             Project: Shiro
>          Issue Type: Dependency upgrade
>          Components: Web
>    Affects Versions: 1.7.0
>            Reporter: Boris Petrov
>            Priority: Blocker
>
> Jakarta EE 9 is out already along with stable versions of the two most 
> popular containers - Tomcat 10 and Jetty 11. `shiro-web` internally still 
> uses `javax` (e.g. `import javax.servlet.ServletContextEvent` in 
> `EnvironmentLoaderListener`) 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.
> Similar to:
> https://issues.apache.org/jira/browse/SHIRO-750



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to