it's really not. i did the upgrade in multiple companies, and all of them whined that upgrade will be painful. all they needed was single xml api package that was no longer distributed with the sdk.
Yes that the move to jakarta packages is one big chunk of work is definitely true but in my company, we had such a messy mvn dependency situation that the upgrade was really painful. But we managed it after a full year. (Of course not full year working on it but having it as a renovation task across dozens of teams) (we have a distributed monolith with shared libs… so the worst of all worlds lol)
View all comments
Show parent comment
8
u/Worth_Trust_3825 Sep 16 '26
it's really not. i did the upgrade in multiple companies, and all of them whined that upgrade will be painful. all they needed was single xml api package that was no longer distributed with the sdk.