Yes, it's a pain that javax. packages in Jakarta EE were renamed to jakarta. and shame for Oracle. We at OmniFish are researching how to make the migration as smooth as possible and we started with a series of blog posts to provide guidance how to migrate with as little pain as possible: omnifish.ee/2023/05/06/how-to-upgr....
We're going to add more articles with examples and explanations. Those guides are related to GlassFish 7 but can be applied to any project that needs to migrate from javax. prefix to jakarta. And yes, a big part of the trick is using Eclipse Transformer, but we plan to explain how to use it effectively. We've already successfully migrated a few projects to Jakarta EE 10 and GlassFish 7, which faces a lot of the problems you wrote about (some dependencies have support for both javax. and jakarta., some only support javax., some have dependencies on other artifacts that depend on javax.).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, it's a pain that javax. packages in Jakarta EE were renamed to jakarta. and shame for Oracle. We at OmniFish are researching how to make the migration as smooth as possible and we started with a series of blog posts to provide guidance how to migrate with as little pain as possible: omnifish.ee/2023/05/06/how-to-upgr....
We're going to add more articles with examples and explanations. Those guides are related to GlassFish 7 but can be applied to any project that needs to migrate from javax. prefix to jakarta. And yes, a big part of the trick is using Eclipse Transformer, but we plan to explain how to use it effectively. We've already successfully migrated a few projects to Jakarta EE 10 and GlassFish 7, which faces a lot of the problems you wrote about (some dependencies have support for both javax. and jakarta., some only support javax., some have dependencies on other artifacts that depend on javax.).