Hi Andreas,
Thanks for your kind words :)
Just a note, we will try to maintain the branches 1.x / 2.x when moving
on 3.x for main.
- Java 11 LTS has been released on September 2018
- Java 17 LTS has been released on September 2021
- Java 21 next LTS is plan to be release on September 2023
So I think organizations will need to learn to upgrade more efficiently
even if for Java 8 the support is longer.
For a framework as Shiro, we need to adapt, I agree that is not so easy
but our main focus is the Shiro's user community needs :)
regards,
François
On 07/01/2023 07:13, Andreas Reichel wrote:
Greetings!
On Fri, 2023-01-06 at 22:02 -0600, [email protected] wrote:
Current (Shiro 1.x): Java 8, Jakarta 8-10+ ( 9+ via shade / classifier)
Future (Shiro 2.x): Java 11, Jakarta 8-10+ ( 9+ via shade /
classifier), full JPMS module support
As far as I can see it, you just describe the reality.
Lots of dependencies require Java 11 already and supporting any
ancient Java 8 installations is becoming a nightmare. (We have 1 such
client left unwilling to change running system.)
Whoever needs a Java 8 Shiro can easily stick with Shiro 1. The main
question was: would you be willing and have the resources to backport
important security fixes into the Shiro 1 line?
Future (Shiro 3.x): Java 17, Jakarta 9-10+ ( source code uses
jakarta.* packages directly), full JPMS module support
Not sure about this. Given, how long Java 8 is around it will take
many years to migrate from Java 11 to 17 in corporate environments.
Oracle's license roller coaster did not help either.
At the same time its all hypothetical since even Shiro 2 is still
"Future". So no harm in defining a road map and then to adjust it when
time will have come.
Thank you for all your effort! Shiro makes my life easy and allows me
to focus on the real problems.
Cheers
Andreas
