Re: [hibernate-dev] [OGM] WildFly modules imposing versions

On 7 March 2017 at 10:47, Gunnar Morling wrote: >> However there's an import statement which slipped into the >> OgmEntityPersister, just for the sake of javadoc linking. I'm not sure >> if that might be a problem, but it could be worth making sure we >> compile all OGM core

Re: [hibernate-dev] [OGM] WildFly modules imposing versions

> However there's an import statement which slipped into the > OgmEntityPersister, just for the sake of javadoc linking. I'm not sure > if that might be a problem, but it could be worth making sure we > compile all OGM core w/o Search on the classpath. The imported type is not referenced in the

Re: [hibernate-dev] [OGM] WildFly modules imposing versions

Hibernate Search was meant to be an *optional* dependency of Hibernate OGM core: - org.hibernate.ogm.cfg.impl.HibernateSearchIntegration.searchIsAvailable() However there's an import statement which slipped into the OgmEntityPersister, just for the sake of javadoc linking. I'm not sure if that

Re: [hibernate-dev] [OGM] WildFly modules imposing versions

I'll have a look,I would expect that modules with the same family would work. I suspect we used the specific version instead of the family version somewhere, I'll check Davide On Tue, Mar 7, 2017 at 9:43 AM, Emmanuel Bernard wrote: > I’ve upgraded the OGM demo to OGM

[hibernate-dev] [OGM] WildFly modules imposing versions

I’ve upgraded the OGM demo to OGM 5.1 Final (from CR1). Again I’ve got deployment errors because it does not find the specific search version: 5.6.1.Final. I had 5.6.0.Final in my WF module deployment. Is that the behavior we want? Do we want the OGM module to impose specific versions of