Re: [DISCUSS] CXF 3.5.x and beyond
Hey Jim, AFAIR this particular topic has popped up several times, a few issues exist [1] and @Christian even did the POC several years ago [2] in attempt to remove some of the hard Spring dependencies (I don't know the outcomes to be fair but I suspect it turned out to be much more difficult than anticipated). The suggestion I have in mind is to keep JDK-17 baseline **for now** and continue working on addressing the blockers (there too many at this point). Once we get to the state when the Jakarta branch is at least buildable / deployable, we could reassess the Spring coupling. I am just afraid doing everything at once would introduce instability in codebase and slow down everyone on either of these efforts. Not sure if you agree but in any case I am definitely +1 for reducing the scope of dependencies on Spring, even in 3.4.x / 3.5.x release lines. Thank you. [1] https://issues.apache.org/jira/browse/CXF-5477 [2] https://github.com/apache/cxf/tree/poc-remove-spring-bp Best Regards, Andriy Redko JM> I accidentally clicked the send button, please ignore my previous email JM> and look at this reply. JM> On Sat, Jan 29, 2022 at 7:58 PM Jim Ma wrote: >> On Mon, Dec 27, 2021 at 10:49 PM Andriy Redko wrote: >>> Hey guys, >>> A bunch of good things have happened at the end of this year. The 3.5.0 >>> out and we are in a good >>> shape to kick off Jakarta support: the Spring 6 milestones and Spring >>> Boot 3 snapshots are already >>> available. There are tons of things to fix and address, I have created >>> this draft pull request [1] >>> with a first batch of changes and TODOs. Everyone should be able to push >>> changes in there, if not >>> - please let me know, I could give perms / move the branch to CXF Github >>> repo. Hope in the next >>> couple of months we get closer to fully embrace Jakarta. >>> On the not so good news side, Spring 6 has kept JDK-17 baseline. It does >>> not play well with our >>> original plan to stick to JDK-11 baseline for 4.x but I am not sure we >>> have any choice here besides >>> bumping the baseline as well. JM> From the JakartaEE9 release[1]and JakartaEE10 plan[2], it still needs to JM> support JDK11. Jakarta Restful WebService 3.0/3.1 and Jakarta XML Web JM> Services 3.0/3.1 JM> apis are the specifications we need to implement in CXF, so we need to JM> build, run and test implementation with JDK11. JM> Just thinking this loud, is it possible that we make Spring plugable or JM> really optional ? 4.x is the major release and it's the chance JM> to refactor CXF code(like we move spring related source/test to separate JM> module) to build/run/test without Spring with a maven profile. JM> [1] JM> https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9.1ReleasePlan JM> [2] JM> https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee10/JakartaEE10ReleasePlan >>> Happy Holidays guys! >>> [1] https://github.com/apache/cxf/pull/888 >>> JM> On Tue, Sep 7, 2021 at 4:56 AM Andriy Redko wrote: >>> >> Hey Jim, >>> >> No, we don't have a branch just yet, primarily because we depend on the >>> >> few >>> >> snapshots in 3.5.0/master. >>> >> @Colm do you have an idea regarding xmlschema 2.3.0 release timelines? >>> >> @Dan do you have an idea regarding neethi 3.2.0 release timelines? >>> >> At worst, you could create a new branch for this feature, or submit a >>> >> pull request against master which we should be able to re-target later >>> >> against the right branch (should be easy). What do you think? >>> JM> This is a good idea. I'll send a PR against the master, and later we >>> can >>> JM> decide the place to merge. >>> JM> Thanks, Andriy. >>> >> Best Regards, >>> >> Andriy Redko >>> >> JM> Thanks for more updates , Andriy. >>> >> JM> Is there a place/workspace branch, I can send a PR for this >>> change? >>> >> JM> On Fri, Sep 3, 2021 at 9:20 PM Andriy Redko >>> wrote: >>> >> >> Hey Jim, >>> >> >> Thanks a lot for taking the lead on this one. Just want to chime in >>> on a >>> >> >> few points. Indeed, as >>> >> >> per previous discussion in this thread, it seems like it make sense >>> to >>> >> >> provide only the subset >>> >> >> of shaded modules with Jakarta namespace. Also, it was confirmed >>> >> yesterday >>> >> >> that Spring Framework >>> >> >> 6 milestones will be available in November this year but the first >>> >> >> snapshots will be out in late >>> >> >> September / early October, looks pretty promising. One >>> **unexpected** >>> >> part >>> >> >> of the announcement >>> >> >> is JDK17 baseline for Spring Framework & Co, that could be a bummer >>> but >>> >> I >>> >> >> have the feeling that >>> >> >> it will be lowered to JDK11. Thank you. >>> >> >> Best Regards, >>> >> >> Andriy Redko >>> >> >> JM> Good point, Romain. We need to look at what to do to make sure >>> all >>> >> >> JM> artifacts are included and transformed if this becomes a cxf >>> module. >>> >> >> J
Re: [DISCUSS] CXF 3.5.x and beyond
I accidentally clicked the send button, please ignore my previous email and look at this reply. On Sat, Jan 29, 2022 at 7:58 PM Jim Ma wrote: > > > > On Mon, Dec 27, 2021 at 10:49 PM Andriy Redko wrote: > >> Hey guys, >> >> A bunch of good things have happened at the end of this year. The 3.5.0 >> out and we are in a good >> shape to kick off Jakarta support: the Spring 6 milestones and Spring >> Boot 3 snapshots are already >> available. There are tons of things to fix and address, I have created >> this draft pull request [1] >> with a first batch of changes and TODOs. Everyone should be able to push >> changes in there, if not >> - please let me know, I could give perms / move the branch to CXF Github >> repo. Hope in the next >> couple of months we get closer to fully embrace Jakarta. >> >> On the not so good news side, Spring 6 has kept JDK-17 baseline. It does >> not play well with our >> original plan to stick to JDK-11 baseline for 4.x but I am not sure we >> have any choice here besides >> bumping the baseline as well. > > > From the JakartaEE9 release[1]and JakartaEE10 plan[2], it still needs to support JDK11. Jakarta Restful WebService 3.0/3.1 and Jakarta XML Web Services 3.0/3.1 apis are the specifications we need to implement in CXF, so we need to build, run and test implementation with JDK11. Just thinking this loud, is it possible that we make Spring plugable or really optional ? 4.x is the major release and it's the chance to refactor CXF code(like we move spring related source/test to separate module) to build/run/test without Spring with a maven profile. [1] https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9.1ReleasePlan [2] https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee10/JakartaEE10ReleasePlan > >> >> >> Happy Holidays guys! >> >> [1] https://github.com/apache/cxf/pull/888 >> >> JM> On Tue, Sep 7, 2021 at 4:56 AM Andriy Redko wrote: >> >> >> Hey Jim, >> >> >> No, we don't have a branch just yet, primarily because we depend on the >> >> few >> >> snapshots in 3.5.0/master. >> >> >> @Colm do you have an idea regarding xmlschema 2.3.0 release timelines? >> >> @Dan do you have an idea regarding neethi 3.2.0 release timelines? >> >> >> At worst, you could create a new branch for this feature, or submit a >> >> pull request against master which we should be able to re-target later >> >> against the right branch (should be easy). What do you think? >> >> >> JM> This is a good idea. I'll send a PR against the master, and later we >> can >> JM> decide the place to merge. >> JM> Thanks, Andriy. >> >> >> >> >> >> Best Regards, >> >> Andriy Redko >> >> >> JM> Thanks for more updates , Andriy. >> >> JM> Is there a place/workspace branch, I can send a PR for this >> change? >> >> >> JM> On Fri, Sep 3, 2021 at 9:20 PM Andriy Redko >> wrote: >> >> >> >> Hey Jim, >> >> >> >> Thanks a lot for taking the lead on this one. Just want to chime in >> on a >> >> >> few points. Indeed, as >> >> >> per previous discussion in this thread, it seems like it make sense >> to >> >> >> provide only the subset >> >> >> of shaded modules with Jakarta namespace. Also, it was confirmed >> >> yesterday >> >> >> that Spring Framework >> >> >> 6 milestones will be available in November this year but the first >> >> >> snapshots will be out in late >> >> >> September / early October, looks pretty promising. One >> **unexpected** >> >> part >> >> >> of the announcement >> >> >> is JDK17 baseline for Spring Framework & Co, that could be a bummer >> but >> >> I >> >> >> have the feeling that >> >> >> it will be lowered to JDK11. Thank you. >> >> >> >> Best Regards, >> >> >> Andriy Redko >> >> >> >> >> JM> Good point, Romain. We need to look at what to do to make sure >> all >> >> >> JM> artifacts are included and transformed if this becomes a cxf >> module. >> >> >> >> JM> BTW, Spring 6 GA supports jakarta ee9 will come in Q4 2022 : >> >> >> JM> >> >> >> >> >> >> https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6 >> >> >> >> JM> On Fri, Sep 3, 2021 at 6:20 PM Romain Manni-Bucau < >> >> >> rmannibu...@gmail.com> >> >> >> JM> wrote: >> >> >> >> >> >> >> >> Le ven. 3 sept. 2021 à 11:30, Jim Ma a >> écrit >> >> : >> >> >> >> >> >> >>> On Wed, Aug 25, 2021 at 9:39 PM Romain Manni-Bucau < >> >> >> rmannibu...@gmail.com> >> >> >> >>> wrote: >> >> >> >> >> >> Le mer. 25 août 2021 à 13:39, Jim Ma a >> >> écrit : >> >> >> >> >> >> > On Fri, Aug 20, 2021 at 2:10 PM Romain Manni-Bucau < >> >> >> > rmannibu...@gmail.com> wrote: >> >> >> >> >> >> >> Le jeu. 19 août 2021 à 22:45, Andriy Redko >> a >> >> >> >> écrit : >> >> >> >> >>> Hi Romain, >> >> >> >> >>> Sorry for the delayed response. I have been thinking about >> your >> >> >> (and >> >> >> >>> Jim) suggestions >> >> >> >>> and came to surprising conclusion: do we actually need to >> >> >> officially >> >> >> >>> release anything >> >>
Re: [DISCUSS] CXF 3.5.x and beyond
On Mon, Dec 27, 2021 at 10:49 PM Andriy Redko wrote: > Hey guys, > > A bunch of good things have happened at the end of this year. The 3.5.0 > out and we are in a good > shape to kick off Jakarta support: the Spring 6 milestones and Spring Boot > 3 snapshots are already > available. There are tons of things to fix and address, I have created > this draft pull request [1] > with a first batch of changes and TODOs. Everyone should be able to push > changes in there, if not > - please let me know, I could give perms / move the branch to CXF Github > repo. Hope in the next > couple of months we get closer to fully embrace Jakarta. > > On the not so good news side, Spring 6 has kept JDK-17 baseline. It does > not play well with our > original plan to stick to JDK-11 baseline for 4.x but I am not sure we > have any choice here besides > bumping the baseline as well. From the JakartaEE10 release plan[1], it still needs to support JDK11. Jakarta Restful Webservice 3.1 and Jakarta XML Web Services 4.0. Just thinking this loud, is it possible that we make Spring plugable ? In [1] https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee10/JakartaEE10ReleasePlan > > > Happy Holidays guys! > > [1] https://github.com/apache/cxf/pull/888 > > JM> On Tue, Sep 7, 2021 at 4:56 AM Andriy Redko wrote: > > >> Hey Jim, > > >> No, we don't have a branch just yet, primarily because we depend on the > >> few > >> snapshots in 3.5.0/master. > > >> @Colm do you have an idea regarding xmlschema 2.3.0 release timelines? > >> @Dan do you have an idea regarding neethi 3.2.0 release timelines? > > >> At worst, you could create a new branch for this feature, or submit a > >> pull request against master which we should be able to re-target later > >> against the right branch (should be easy). What do you think? > > > JM> This is a good idea. I'll send a PR against the master, and later we > can > JM> decide the place to merge. > JM> Thanks, Andriy. > > > > > >> Best Regards, > >> Andriy Redko > > >> JM> Thanks for more updates , Andriy. > >> JM> Is there a place/workspace branch, I can send a PR for this change? > > >> JM> On Fri, Sep 3, 2021 at 9:20 PM Andriy Redko > wrote: > > >> >> Hey Jim, > > >> >> Thanks a lot for taking the lead on this one. Just want to chime in > on a > >> >> few points. Indeed, as > >> >> per previous discussion in this thread, it seems like it make sense > to > >> >> provide only the subset > >> >> of shaded modules with Jakarta namespace. Also, it was confirmed > >> yesterday > >> >> that Spring Framework > >> >> 6 milestones will be available in November this year but the first > >> >> snapshots will be out in late > >> >> September / early October, looks pretty promising. One **unexpected** > >> part > >> >> of the announcement > >> >> is JDK17 baseline for Spring Framework & Co, that could be a bummer > but > >> I > >> >> have the feeling that > >> >> it will be lowered to JDK11. Thank you. > > >> >> Best Regards, > >> >> Andriy Redko > > > >> >> JM> Good point, Romain. We need to look at what to do to make sure > all > >> >> JM> artifacts are included and transformed if this becomes a cxf > module. > > >> >> JM> BTW, Spring 6 GA supports jakarta ee9 will come in Q4 2022 : > >> >> JM> > >> >> > >> > https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6 > > >> >> JM> On Fri, Sep 3, 2021 at 6:20 PM Romain Manni-Bucau < > >> >> rmannibu...@gmail.com> > >> >> JM> wrote: > > > > > >> >> >> Le ven. 3 sept. 2021 à 11:30, Jim Ma a > écrit > >> : > > > > >> >> >>> On Wed, Aug 25, 2021 at 9:39 PM Romain Manni-Bucau < > >> >> rmannibu...@gmail.com> > >> >> >>> wrote: > > > > >> >> Le mer. 25 août 2021 à 13:39, Jim Ma a > >> écrit : > > > > >> >> > On Fri, Aug 20, 2021 at 2:10 PM Romain Manni-Bucau < > >> >> > rmannibu...@gmail.com> wrote: > > > > >> >> >> Le jeu. 19 août 2021 à 22:45, Andriy Redko > a > >> >> >> écrit : > > >> >> >>> Hi Romain, > > >> >> >>> Sorry for the delayed response. I have been thinking about > your > >> >> (and > >> >> >>> Jim) suggestions > >> >> >>> and came to surprising conclusion: do we actually need to > >> >> officially > >> >> >>> release anything > >> >> >>> to shade/overwrite javax <-> jakarta? Generally, we could > shade > >> >> >>> Spring or/and any other > >> >> >>> dependency but we would certainly not bundle it as part of > CXF > >> >> >>> distribution (I hope you > >> >> >>> would agree), so not really useful unless we publish them. As > >> such, > >> >> >>> probably the best > >> >> >>> interim solution is to document what it takes to shade CXF > >> (javax > >> >> <-> > >> >> >>> jakarta) and let > >> >> >>> the end users (application/service developers) use that when > >> >> needed? > >> >> >>> In this case > >> >> >>> basically CXF, Spring, Geronimo, Swagger, ... would follow > the > >> same > >> >> >>> shading rules.
