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?
COh> Colm.
COh> On Thu, Jan 10, 2019 at 10:28 AM Dennis Kieselhorst <[email protected]> wrote:
>> > Can you update JAX-WS + SAAJ when the JAXB switch is done and working?
>> Yes. The question is when do we update the other stuff (Activation,
>> Annotation, CDI, EL, Mail, Validation, JSON, ...)? I'd like to have it
>> clean for 3.3.0 but it's kind of transitive dependency hell.
>> > Do
>> > you know when they plan to release 4.0.2?
>> >
>> Just discussed on the list with Mark Thomas:
>> https://www.eclipse.org/lists/servlet-dev/msg00069.html
>> So probably this will take some more days...
>> Regards
>> Dennis
