rmannibucau commented on pull request #737: URL: https://github.com/apache/cxf/pull/737#issuecomment-751221147
Think the most important is not jakarta but users. So question is: what needs the most dev and maintenance, jakarta or javax - indeed i assume than forking itself is bad and too costly. My opinion is that javax will stay way more used that jakarta for years as of today. New features can be done creating fake org.apache.cxf.spec.jakarta api used for javax flavor - since compat is still a prerequisite - and shaded properly to jakarta when needed. We did it at openwebbeans for cdi 1.1 -> cdi 2 move and it was cheap and efficient. My 2 cts is that it will cost less than moving to jakarta which is a blocker for most users today (dont forget cxf is not alone in a stack and moving a full stack is rarely a success for users and libs as shown by all EE servers). Hope it makes sense. ---------------------------------------------------------------- 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]
