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 stay on Shiro 2 (javax) if Shiro 3 were to come out before that timeframe and it didn't support shading. On Thu, Apr 4, 2024 at 4:42 PM <le...@flowlogix.com> wrote: > Looks like just one comment so far > > > On Apr 4, 2024, at 9:48 AM, Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > > Hi Lenny, > > > > Did you receive comments on this thread ? > > > > Regards > > JB > > > > On Fri, Mar 15, 2024 at 5:10 AM <le...@flowlogix.com> 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 their usage, i.e. jakarta.* > namespace. > >> These and other discussion warrant a few question worth discussing. > >> Please keep in mind by the time Shiro 3.x is released, it could be 2025 > or later. > >> > >> 1) How long should Shiro 1.x be maintained? > >> Not at all? 6 months? 1 year? 2 years? Other? > >> > >> 2) Should Shiro 3 support javax.* namespace via shading at all? > >> Not at all (drop support?) As shaded artifact? As different version > (shiro-core:3.0-javax)? > >> > >> 3) Should Shiro 3 support SpringBoot 2.x or drop support for SB 2.x at > all (requires dropping support for javax namespace) > >> > >> 4) What’s the minimum Java version? > >> Keep it at 11? Switch to 17 (both SpringBoot 3.x and Jakarta EE 11 > require 17+)? Switch to 17? Switch to 21 as minimum version? > >> > >> Any other issues? > >> > > > >
