Hi,
I'm making some tests with the maven-shade-plugin to provide jakarta
classifier for shiro modules that are using javax.* packages.
regards,
François
On 16/05/2022 16:21, - - wrote:
Hi,
+1 from my side for a Shiro version supporting Jakarta EE 9.1
natively. Shiro is the last lib which m
Hi,
+1 from my side for a Shiro version supporting Jakarta EE 9.1 natively. Shiro is the last lib which misses support and because of that Shiro is a showstopper for migration. We are using Websockets and instantiate a ShiroFilter in code, which then takes a servlet con
Hi,
We are also in the process of migrating to Jakarta EE 9/10 and Shiro is one
of the libraries missing native support. Transformers only work on an
application built entirely against JEE8. You simply cannot build your
application with mixed JEE versions. For example, when one method returns
a ja
Hi,
I'm in the process of upgrading my application to Spring 6, Spring Boot 3 and
Hibernate 6. That means moving to the Jakarta APIs. Shiro is my only dependency
that doesn't have a (pre)release based on Jakarta yet.
While most containers will be able to support legacy javax APIs at runtime or
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 tra
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 cen
