On Wed, Dec 13, 2017 at 7:05 AM Sanne Grinovero <sa...@hibernate.org> wrote:
> Not really. Think of it as Deprecation: it will trigger some warnings > for end users, especially those who didn't get the "news" of moving to > the new API, and keep things working for a little longer for those > people not willing (able?) to react right away to resolve the > warnings. > > We can keep a deprecated method (jar) around for a couple more > releases, or drop it as soon as it gets too inconvenient to maintain. > It's definitley not a promise of long term. > Couple more releases of what? Hibernate ORM, as opposed to JPA? I assume that's what you meant, just making sure. Honestly I would never publish a new relocation - that means we are incrementing the version of the JPA API jar, which should not happen. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
