mkarg commented on pull request #737: URL: https://github.com/apache/cxf/pull/737#issuecomment-751225155
> Think the most important is not jakarta but users. I think you misunderstood the target of *this* PR: It is *solely* to provide Jakarta EE 9+ compatible CXF. Anything else is certainly welcome and worth a discussion, but definitively *not* what *this* PR covers. And definitively *not* what I can and will put efforts into, as my *sole* target here is to help CXF with Jakarta EE 9+ compliance. I am no a typical CXF contributor, I am just a Jakarta EE ambassador at CXF. Also note that the Jakarta WG (including Oracle, IBM, Red Hat, *and Tomitribe*) decided that Jakarta EE 9.1 released in 2021 will put minimal Java level to 11, and that these companies actively plan Jakarta EE 9.1+ compatible implementations (i.e. *including* new `jakarta.*`*-only* APIs) compatible implementations within rather near future (Jersey will switch to Jakarta EE 9.1 within the next few months actually; the namechange is already done months ago. Hence GlassFish, hence Payara, will be `jakarta`-namespaced rather soon, hence their customers will do the switch **eagerly** and at the Jakarta EE marketing committee we working very hard to convince tool vendors and application authors to do it **right now** to be prepared for that very moment). The `javax` namespace is definitively **dead**, i.e. MUST NOT get extended *in any way*. This means, if your customers stick with `javax`, they *soley* will get bug fixes, but never new features (at least on an API level). I doubt that many customers understood that so far. They MUST rewrite their applications to `javax` to use **any** new API-level features, so that's why I really plea for branching CXF into a `javax` sustained branch and a `jakarta` branch. Everything else will *not* cover the actually existing needs for new features of CXF customers. In fact I do not see much space for any other decision. Either you want to become Jakarta compliant one day, or you do not. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
