[
https://issues.apache.org/jira/browse/SHIRO-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068719#comment-17068719
]
Brian Demers commented on SHIRO-750:
------------------------------------
This would be a breaking change. So it would need to wait for a 2.0. unless we
could support both versions in tandem.
As with the servlet-api Shiro implements some of these interfaces.
That said, to your point, the current dependency should probably be marked with
the `provided` scope.
Are there any bridge implementations that allow libraries to support both APIs?
> Migrate to jakarta APIs
> -----------------------
>
> Key: SHIRO-750
> URL: https://issues.apache.org/jira/browse/SHIRO-750
> Project: Shiro
> Issue Type: Improvement
> Components: jax-rs
> Affects Versions: 1.5.2
> Reporter: Benjamin Marwell
> Priority: Minor
>
> Hi,
> {{javax.}}-dependencies have been superseeded by jakarta dependencies.
> In:
> [https://github.com/apache/shiro/blob/master/support/jaxrs/pom.xml]
> We can replace the rs-api artifact with:
> {code:java}
> <dependency>
> <groupId>jakarta.ws.rs</groupId>
> <artifactId>jakarta.ws.rs-api</artifactId>
> <version>?</version>
> </dependency>
> {code}
> BTW, any reason for not making it optional and provided? EE APIs are usually
> provided by the application container. There is no need to ship it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
