It wasn't noise, I updated the documentation to use the new short names:
https://github.com/hibernate/hibernate-orm/commit/f8964847dd40f64e1f478eba47c767be98742125
This is what you should use from now on.
Cheers
On Thu, Jul 19, 2018 at 9:08 PM Laurent Almeras wrote:
> Mistake on my side. As I
Mistake on my side. As I configure programmaticaly Hibernate, I use
.class.getName() code to populate my Hibernate properties. So I
directly stepped into a class not found error when I update.
I just modify my code to use strings provided in documentation and it
works as expected. So not sure a
By the way, did you have an error using the old names?
Because they should still be supported.
On Thu, Jul 19, 2018 at 10:16 AM Guillaume Smet
wrote:
> Hi Laurent,
>
> Good catch. The classes have been moved to an internal package and we
> should now use the short names instead.
>
> Created htt
Hi Laurent,
Good catch. The classes have been moved to an internal package and we
should now use the short names instead.
Created https://hibernate.atlassian.net/browse/HHH-12829, will fix right
away.
--
Guillaume
On Wed, Jul 18, 2018 at 11:43 PM Laurent Almeras wrote:
> Hi,
>
> Sorry to bot
Hi,
Sorry to bother you on a deprecated feature subject, but I think the
package names provided in documentation are broken :
https://docs.jboss.org/hibernate/stable/orm/userguide/html_single/Hibernate_User_Guide.html#caching-provider-ehcache-region-factory
Do we agree that the correct names ar
