Dependencies for the org.hibernate.search.orm module are defined this way:

    <dependencies>
        <module name="javax.transaction.api" />
        <module name="org.hibernate" slot="${hibernate-orm.module.slot}" />
        <module name="org.hibernate.commons-annotations" />
        <module name="org.hibernate.search.engine" export="true" services="import" slot="${hibernate.search.version}" />
        <module name="org.jboss.logging" />
        <module name="javax.persistence.api" />
    </dependencies>

With ${hibernate-orm.module.slot} being replaced with 5.2.

From what I understand, this means in particular that if a 5.3 version of Hibernate ORM is released, then even if Hibernate Search 5.7 works well with ORM 5.3, users won't be able to upgrade Hibernate ORM because we explicitly mandate the use of ORM 5.2 only.

>From what I can see, we started to state the required version explicitly when upgrading the WildFly integration tests. If it was only for testing purpose, maybe we could find another solution? I don't know if it's possible, but one thing that comes to mind is to override the module in the "main" slot of Hibernate ORM to be the one in the "5.2" slot.

Note that I may be mistaken, since I don't know much about WildFly (yet)... Any opinion is welcome.