I guess jakarta will "relocate" ([1]) the jars so frameworks will start getting warnings and fix it so sounds like a move forward anyway.
Side note: we got the same issue with geronimo spec jars for years and it never had been a real issue in practise so not a big deal IMHO. [1] https://maven.apache.org/guides/mini/guide-relocation.html Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le jeu. 10 janv. 2019 à 16:54, Dennis Kieselhorst <[email protected]> a écrit : > > > For me, as a CXF user, the easiest way would be to get the old artifacts, > > as I expect other frameworks > > that I already have in the project would still use the existing Maven > > coordinates and then I will have a mix of old and new coordinates until > all > > of them upgrade. > > Hi Andrei, > > I understand your concerns. I don't like the renaming too as there is no > benefit and this causes lots of effort. But at some point in time every > framework will pick up the new coordinates and you have to deal with it. > If you want to keep the old ones, you can just add an exclusion or stick > to CXF 3.2.x. > > Regards > Dennis >
