+1 to release, there are too much forks out there already so better to release partially than not release at all IMHO
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le lun. 7 nov. 2022 à 14:25, Misagh <[email protected]> a écrit : > Hello all, > > If possible, I'd like to ask that you allow v4 to ship with a new > release of wss4j that would contain this change: > https://github.com/apache/ws-wss4j/pull/62 > > At the moment, OpenSAML v5 is not released yet, but it is anticipated > to be GA before end of this year, hopefully. > > On Mon, Nov 7, 2022 at 12:19 PM Jim Ma <[email protected]> wrote: > > > > Hi all, > > After 9 months of work, we finally fixed/worked around all issues for > > Jakarta support. Now all the cxf tests are passed: > > https://ci-builds.apache.org/job/CXF/job/CXF-JDK17/848/ and we can say > that > > CXF successfully migrated to Jakarta namespace(and support Jakarta > EE9.1). > > To get cxf jakarta artifacts/binary available for the CXF community > > especially the user who asked for this jakarta artifacts like [1] and > get > > more feedback from our community, do you think it's time to release the > CXF > > 4.0.0 and what else do you think we should have in this new jakarta > release > > ? > > > > [1]https://lists.apache.org/thread/kwfg2s5gj72tkgn5c5vdcsvtgdkdm6dl > > > > Thanks, > > Jim >
