Hi all, there's a conflict in the Javassist versions of the WildFly modules of Hibernate ORM 5.2.4.Final, but I'm not sure how to proceed as I'm not familiar with this functionality. The module declares *both*: - a dependency to the WildFly provided Javassist: <module name="org.javassist"/> - inclusion of Hibernate's own version of Javassist: <resource-root path="javassist-3.20.0-GA.jar"/> Having both is causing trouble as they are both visible to the Hibernate classloader; however I couldn't score a quick win with the testsuiste by disabling either (all tests using these modules in the Hibernate Search testsuite fail). I suspect the problem is that JipiJapa also depends on the <module name="org.javassist"/>, while ORM obviously needs the more recent version of it. I'm not familiar with what JipiJapa's business around Javassist; could we keep the two clearly separated? Especially if we want to make Byte Buddy a viable alternative, I suspect the solution is that JipiJapa should not depend on Javassist directly, but invoke a generic instrumentation SPI on Hibernate; also with JipiJapa not able to see Javassist at all, we'd be in control of the one and only Javassist version visible to ORM: the one we compile and test with. Thanks, Sanne