Changing javax to jakarta

[Mihai Nita]

I've tried to update our dependencies to the latest release versions.

And things fail, because some of them renamed the javax namespace to jakarta

https://blogs.oracle.com/javamagazine/transition-from-java-ee-to-jakarta-ee

https://nipafx.dev/jakarta-ee-javax-and-a-week-of-turmoil/

https://www.infoq.com/news/2019/07/javaee-specs-renamed-jakarta/

https://www.baeldung.com/java-enterprise-evolution

It touches JSRs, Glassfish, etc.

We have about 1500 instances, most of them in javax.xml:

  [1] javax.swing

  [2] javax.crypto
  [4] javax.imageio
  [7] javax.ws
  [8] javax.json
  [1704] javax.xml

I can work on doing the migration.

But I wanted to make sure that everybody is OK with it :-)

Cheers,

Mihai

[Mihai Nita]

It looks like we have 1700 or so :-)

There are about 1500 lines. I've counted different things.

Mihai

[jim]

Mihai, as far as I understand we don't really have a choice if we want to use the latest versions. I'm ok to make the changes.

Jim

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/CAK69zbkRz-YHzf8eyNxSvsyosvcwpSvV02Cw9hiO932q7Zkomw%40mail.gmail.com.

[Mihai Nita]

Yes, in the long run we have no choice.

But we can delay it, if someone has a big blocker.

Mihai

[Mihai Nita]

This is all it takes:

https://bitbucket.org/okapiframework/okapi/commits/f9ea2806c81eba0363b8357f996f1bf75ddb99e8

Looks like some of the new libraries decided to still keep the javax namespace.

The only tricky thing was to find the right replacements.

Mihai

[Mihai Nita]

The javax - jakarta move is done and working fine in a branch (mihai_javax2jakarta)
https://bitbucket.org/okapiframework/okapi/commits/f9ea280

M.