Re: [hibernate-dev] [OGM] Validating our artifacts don't rely on JBoss-only dependencies

2018-02-22 Thread Yoann Rodiere
> The integrationtest folder is more to test the hibernate-ogm-modules > and have some > checks that the dialects work with WildFly really. I could move the current integration tests to integrationtest/wildfly and create a new integrationtest/infinispan-remote module? Then it would be clear which

Re: [hibernate-dev] [OGM] Validating our artifacts don't rely on JBoss-only dependencies

2018-02-22 Thread Davide D'Alto
Not sure about it, those are specific integration tests for infinispan remote. The integrationtest folder is more to test the hibernate-ogm-modules and have some checks that the dialects work with WildFly really. > after all, since they need a running Infinispan server to work. All the tests in

[hibernate-dev] [OGM] Validating our artifacts don't rely on JBoss-only dependencies

2018-02-22 Thread Yoann Rodiere
Hello, TL;DR: can I move hibernate-ogm-infinispan-remote tests to the integrationtest module, since they are actually integration tests? During one of our previous IRC meetings, I mentioned that we did some changes in the Hibernate Search POMs to remove the need for custom settings when