I have tested Jakarta 1.11.x with JPMS and it will not have split package issue (when released) Also, as François said, 1.11.x will have Jakarta modules released as well.
Latest Shiro 2.0.0-SNAPSHOT already has Jakarta modules and JPMS split packages fixed. On 2022/11/24 20:51:39 le...@flowlogix.com wrote: > Since Shiro is an unnamed module and is on the Classpath (not modulepath) the > split packages should not be a problem, I would think. > > > On Nov 24, 2022, at 6:41 AM, Francois Papon <fr...@openobject.fr> wrote: > > > > Ok for the first one (jakarta package) we will publish it with the next > > 1.11.x but for the JPMS as it's a breaking change I'm afraid that we cannot > > provided it on 1.x... > > > > On 24/11/2022 11:10, Alex Orlov via user wrote: > >> Hi Francois, > >> I need two things — jakarta.servlet (not javax.servlet) and JPMS support > >> (split package problem must be resolved). > >> > >> On 2022/11/24 09:26:04 fpapon wrote: > >>> Hi Alex, > >>> > >>> It's recommended to use a SNAPSHOT in production and the 2.x version is > >>> not already finished. > >>> > >>> For the released date, we need to have a discussion into the team to > >>> define what we want to put in this first release because the big part is > >>> about api breaking changes, so we need to well documented the migration > >>> guide.for > >>> > >>> Can you explain more which part of 2.0 for Servlets and REST do you need > >>> vs 1.x? > >>> > >>> regards, > >>> > >>> Francois > >>> > >>> On 24/11/2022 09:14, Alex Orlov via user wrote: > >>>> Hello. Could anyone answer the following questions: > >>>> > >>>> 1. Can current Shiro 2.0-SHAPSHOT use used in production (we need it > >>>> only for servlets and REST) > >>>> 2. When will Shiro 2.0 be released? > >>>> > >>>> -- > >>>> Best regards, Alex Orlov > >>> > >>> -- > >>> -- > >>> François > >>> > >> -- > >> Best regards, Alex Orlov > >
