Hacker News Reader

Technically easy, but thought to expose that new JVM legally.

You would probably rather write a JVM agent that changes the class references.

Eclipse will almost surely fork the namespace to something jakarta related.

Which turns to to be quite easy:

https://twitter.com/rafaelcodes/status/1125032183167688706

The other option is a maven plugin that lets you rename packages and then someone posts a list of rules on a StackOverflow question for renaming the new namespaces to the old ones: that way, no JDK distributor is distributing software that understands the old package names.

Maybe have a more sensible namespace convention. Presently, for any given API, it's a toss up of whether it's under javax.* or java.*, with no rhyme or reason.