You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jakarta 3 brings us a new package structure replacing javax.* with jakarta.*.
As I understand it, in transaction-outbox project, this migration had happened while hibernate validator was updated from 6 to 7. So now, we have a lot of jakarta.* imports across the project. This causes a lot of troubles because a vast majority of libraries and frameworks (e.g. the newest spring boot) still use jakarta 2 with javax.* imports, so you need to use an older version of transaction-outbox in this case to make the code compile.
Is it possible to do something with it? We can downgrade hibernate validator or keep two versions of transaction-outbox? Or even refactor classes with potential problems to make them independent from it.
The text was updated successfully, but these errors were encountered:
We've been hit with this at Goji too and are frozen on an earlier version.
It's actually looking like a mistake to have taken this hibernate-validator update into the project. I am tempted to revert the related commits in master and jump up a major version of transaction-outbox.
Happy to take a PR , but if not I'll probably do this in the next few weeks.
Jakarta 3 brings us a new package structure replacing
javax.*
withjakarta.*
.As I understand it, in transaction-outbox project, this migration had happened while hibernate validator was updated from 6 to 7. So now, we have a lot of
jakarta.*
imports across the project. This causes a lot of troubles because a vast majority of libraries and frameworks (e.g. the newest spring boot) still use jakarta 2 withjavax.*
imports, so you need to use an older version of transaction-outbox in this case to make the code compile.Is it possible to do something with it? We can downgrade hibernate validator or keep two versions of transaction-outbox? Or even refactor classes with potential problems to make them independent from it.
The text was updated successfully, but these errors were encountered: