It is all utterly inconsistent, of course, with javax.persistence developed outside of Oracle (under Eclipse) and so being renamed (just to add pain to its users), and javax.jdo developed outside of Oracle (under Apache) and so not being renamed. Anyway, DataNucleus supports any reasonable persistence spec wherever it is developed.

So on further reading I realized Oracle has just separated out JEE stuff to Eclipse. I had previously misunderstood Oracle's stance to imply that all non "core Java" libraries using javax.* packaging were being separated out to jakarta.* land.

Ah cool. It was my understanding that any 'javax.*' packages would have to be renamed.

No. It's nothing to do with 'java ee'.

Will the JDO API have to undergo a similar Jakartification?

DN v6.0.0.m1 is released.

Notable changes are

• Minimum Java requirement v11. Upgraded ASM to v9.1 to provide for all current bytecode.
• Support for Jakarta Persistence v3.0+ API. The JPA API is effectively discontinued at its current v2.2 and it continues life as Jakarta Persistence API. DataNucleus continues to support the JPA API v2.2 for those people who don't want to repackage annotations and API classes for little benefit. For those that want any future benefits from this API they can now make use of Jakarta Persistence API with DataNucleus. You can use metadata (XML/annotations) from any of the persistence specs (JDO, JPA, Jakarta) with any of the persistence API's (JDO, JPA, Jakarta) interchangeably with DataNucleus.
• Various bug fixes and improvements.

Report any problems in the normal way with associated testcase or, better still, get involved and provide Pull Requests.