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, at 4:50 PM, Steve Lopez via user <u...@shiro.apache.org> > wrote: > > 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 and some not (yet) > I've considered migrating to Spring Boot but don't see the cost/benefit given > we don't use embedded Tomcat > > On Thu, Apr 4, 2024 at 5:26 PM Lenny Primak <le...@flowlogix.com > <mailto:le...@flowlogix.com>> wrote: > Thanks for your feedback. > What’s the rest of your stack look like? > If you are using Spring how is the lack of support for Spring 2 handled? > Or do you use something else?. JSF? Vaadin? > >> On Apr 4, 2024, at 3:57 PM, Steve Lopez via user <u...@shiro.apache.org >> <mailto:u...@shiro.apache.org>> wrote: >> >> >> 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 >> <mailto: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 >> > <mailto: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 >> > <mailto: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? >> >> >> > >>
