On Thu, Jan 10, 2019 at 1:59 PM Dennis Kieselhorst <m...@dekies.de> wrote:
> > > It would be great to get CXF out soon enough, since more and more > projects switch > > to Java 11. From practical standpoint, releasing CXF 3.3.0 with JAXB > deps would > > make a lot of sense (in my opinion), since every other project around > did exactly > > that. However, we've already started moving to Jakarta EE artifacts. > Should it be > > reverted (to "old" ones)? Or should we wait for Jakarta EE to publish > others? > > Releasing CXF with the mix of both is not looking good I think. Thoughts? > > > > Best Regards, > > Andriy Redko > > > > COh> I'm a bit concerned that we we delay indefinitely, when we need to > get a > > COh> release out that supports Java 11. Perhaps CXF 3.3.0 should just > contain > > COh> the JAXB upgrade and let CXF 3.4.0 pick up all of the newer > dependencies? > > > Let's focus on JAX-WS and JAX-RS (along with JAXB) for 3.3.0 as those > are the main implementations that we are offering. Everything else can > be done for 3.4.0. > > I also agree that we should release soon (maybe next week?) and avoid > another delay. > > Regards > Dennis > For me, as a CXF user, the easiest way would be to get the old artifacts, as I expect other frameworks that I already have in the project would still use the existing Maven coordinates and then I will have a mix of old and new coordinates until all of them upgrade. Regards, Andrei
