The move from javax to jakarta was not really connected to the changes in the language. It is very much recommended to not do these upgrades simultaneously.

▲

MBCook 2 days ago | parent | next [-]

Right. It was a copyright issue, I know.

We didn’t do that one giant jump. We moved from 8 to 17 in one step, then in a separate step upgraded Tomcat requiring the jakarta changes later.

I guess I tend to think of them as one “modernizing“ combo even though they’re not.

	▲	samus 2 days ago \| parent [-]
		Indeed, exactly the same process we did.

▲

cesarb 2 days ago | parent | prev [-]

> The move from javax to jakarta was not really connected to the changes in the language.

It sort of was; it was caused by Java no longer coming with the J2EE libraries. Before that, J2EE could be considered part of Java; now that it's a separate project, they were forced to rename the packages.

	▲	samus 2 days ago \| parent [-]
		The JDK didn't come with these packages anymore. They were never part of core Java.