Hi,
Since Shiro 2.0-alpha and 2.0 Final has been released, most, if not all
questions we have been getting are about Jakarta EE integration.
Mostly regarding shaded artifacts and their usage, i.e. jakarta.* namespace.
These and other discussion warrant a few question worth discussing.
Please keep
Hi Lenny,
Did you receive comments on this thread ?
Regards
JB
On Fri, Mar 15, 2024 at 5:10 AM wrote:
>
> Hi,
>
> Since Shiro 2.0-alpha and 2.0 Final has been released, most, if not all
> questions we have been getting are about Jakarta EE integration.
> Mostly regarding shaded artifacts and t
Looks like just one comment so far
> On Apr 4, 2024, at 9:48 AM, Jean-Baptiste Onofré wrote:
>
> Hi Lenny,
>
> Did you receive comments on this thread ?
>
> Regards
> JB
>
> On Fri, Mar 15, 2024 at 5:10 AM wrote:
>>
>> Hi,
>>
>> Since Shiro 2.0-alpha and 2.0 Final has been released, most,
I see… Spring Framework isn’t EOL until sometime this year though (soon),
do you plan to use commercial support to extend its life?
Or just plan to see how long you can “take” the staleness before upgrading to
Jakarta namespace?
Thanks for the great feedback, it’s very valuable.
> On Apr 4, 2024
- Spring MVC 5.3
- Combination of legacy JSP, JSTL, Thymeleaf and JSF/Tiles (that
probably begs questions; multiple apps developed over several decades and
limited resources to address tech debt)
- A number of 3rd party library dependencies; some having migrated to
Jakarta-EE a
I would be curious how many shiro projects are still on Tomcat 9 given the
heavy lift to migrate to Jakarta-EE.
We're on Java 17, Tomcat 9 & Shiro 1.13. While we plan to migrate to
Jakarta-EE (and Tomcat 10) it'll likely be at least a year before it can
fit in the roadmap. So we would need to
