mkarg commented on pull request #737: URL: https://github.com/apache/cxf/pull/737#issuecomment-751338912
You are mixing things here. The Jakarta EE WG decided the big bang certainly *only for EE*, not for third parties; the intention was to get past this mixing situation ASAP, and the big vendors *agreed* to that plan, as it is the *smaller* pain. Now you pick *third parties* to proof "nobody" did -- after just few week! This is ridiculous, as we all are just in the migration phase. First, certainly *third party* libs are free to adopt or not adopt the new namespace as they like. Second, the Jakarta namespace is here since *few weeks* only, and certainly it needs months until third parties adopted it. But in the end, the `javax` namespace definitively *is dead* and there is no value in keeping it for long. Jersey for example eargerly switched the master branch (3.x), but everybody can run javax-namespaced legacy applications on a still maintained sustained branch (2.x) -- just what I proposed and what is totally fine for users. Nobody is *ever* allowed to extend `javax` in any way, s o **eventually** every lib, and every direct implementation, like CXF, *must* either adopt the namespace, or deal with *more and more* tweaks. For example, in EE 10 there will be backwards-incompatible changes in JAX-RS, so the stack of tweaks will pile higher and higher. Anyways, I still do not see where my statements where wrong and even more, I do not understand what this discussion is all about. I already told you, CXF can do as they please, I have no strong feelings about CXF at all, so why keep insulting me? ---------------------------------------------------------------- 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: us...@infra.apache.org