Re: [infinispan-dev] Proposal for moving Hibernate 2l provider to Infinispan

Just a heads up - FWIW I doubt my reply goes through to the entire infinispan-dev list. Replies inline... 3. What should be the artifact name? Should it be 'hibernate-infinispan' Since you use Maven (IIUC) you could just publish a relocation... 4. Should the main artifact contain the hibernate major version it belongs Probably, but (no promises) one thing I wanted to look at since Hibernate baselines on Java 8, is to maintain the existing SPI using default methods as a bridge. But failing that, I think your suggestion is the best option. FWIW Hibernate offers "short naming" or "friendly naming" for many configurable settings, cache providers being one. For hibernate-infinispan we register 2: "infinispan" and "infinispan-jndi". You can see this in org.hibernate.cache.infinispan.StrategyRegistrationProviderImpl. That approach will continue to work when you move it. The point being that users do not specify the class name in config, they'd just specify "infinispan", "infinispan-jndi", etc. 6. Testing wise, the cache provider is currently tested one test at the Hmmm, that is actually surprising... I thought the hibernate-infinispan provider tests were still disabled as they had routinely caused intermittent failures of the build. I guess this was rectified?