Drop hibernate-infinispan module - relocated

I agree about the short names over the class names. I forgot about the short naming for caching when I mentioned that earlier

IMO, we should keep the short names consistent and not trying to retrofit class name refactorings. Under Java 9 rules, we'd have issues if two different artifacts out there would share same package name. So, I'd rather avoid that.

Radim Vansa Galder Zamarreno Paul Ferraro What is the GAV of the new artifact?

It depends. Latest Hibernate supported artifact would always be:

org.infinispan:infinispan-hibernate-cache

Currently latest would be Hibernate 5.2.

We'd also support Hibernate 5.1 whose GAV would be:

org.infinispan:infinispan-hibernate-cache-v51

btw, the other (preferred) option is to make sure you change the "short name" registrations for the Infinispan L2 cache provider. These used to be controlled by the service (JDK service) org.hibernate.cache.infinispan.StrategyRegistrationProviderImpl. Specifically we used to register 2 different short names:

• "infinispan" (or "InfinispanRegionFactory") -> org.hibernate.cache.infinispan.InfinispanRegionFactory

• "infinispan-jndi" (or "JndiInfinispanRegionFactory") -> org.hibernate.cache.infinispan.JndiInfinispanRegionFactory

We always suggest users use these short names to protect against "refactoring" changes. If you simply update those registrations, you could choose to not re-introduce the same FQN

Thanks . already has the relocation set up - so we should be good to go for ORM 5.3