It's pretty simple really. It's about having a new impetus for the CXF
development.
Without a Java 9 only master CXF will be about fixing the bugs only.
JAX-WS is done long time ago, next version of JAX-RS will take N amount
of time to materialize.
Java 9 with its Flow class will let CXF do new work around Reactive
support. It will have new features that only work with Java 9 and may
give new ideas for the contributions.
3.2.x is at the start of its life-cycle and will have a couple of years
at least for it to retire, giving Java 8 support.
3.1.x has probably 6 months or so left in it, and after it's gone we
will have 3.2.x and 4.0.x or whatever new version is preferred.
Sergey
On 16/11/17 08:15, Dennis Kieselhorst wrote:
On 2017-11-16 07:27, Christian Schneider <ch...@die-schneider.net> wrote:
I dont think we can already predict when users move to Java 9.
So creating a Java 9 only branch at this time means we have to maintain two
main branches over a long time.
What is the rationale behind a Java 9 only branch compared to being Java 9
and Java 8 compatible on master?
I also don't see a good reason to do that at the moment. Let's release the XJC
plugin and users should be able to use CXF with Java 9 or am I missing
something?
Cheers
Dennis
