Switch from JPA 2 to JPA 3: renaming all package and properties use to jakarta.persistence
Description
Activity
Christian Beikov December 23, 2022 at 1:05 PM
Already did that for 6
Sanne Grinovero January 4, 2021 at 1:01 PM
Hi Yordan,
yes we would also prefer leaving this to 6.0 - that’s why we didn’t release master (5.5 even though we separated the branch from 5.4) since a long time: to keep our options open while we work on 6 but don’t have a release date yet. 6 is maturing quickly now, so we’ll likely never release a JPA3 compatible version based on 5. However some peer projects (like WildFly) need some work-in-progress compatible drop-in to not block related work.
In fact, these changes have been reverted even from master.
Unrelated, but for clarity: Hibernate never claimed to follow semver strictly speaking. But I agree that it would be surprising, and not an optimal solution, to do this in v. 5.
Yordan Gigov December 31, 2020 at 9:07 AM
Question: Isn’t this better left for 6.0, since it breaks backwards compatibility? Generally in semver you should only add features between minor versions, and if you deprecate one it should still be supported until major release.
Too bad there’s no way to support both packages, because exceptions can’t inherit two classes.
A preview is available here: https://github.com/hibernate/hibernate-orm/pull/3373