[hibernate-dev] Javassist dependency conflict in the ORM modules for WildFly

[Scott Marlow]

Hi,

Would it be possible for a WildFly deployment unit processor to detect
Hibernate ORM native applications, by detecting the presence of a
particular configuration file that is always present?  I'm not sure if
this is possible, but if it is, perhaps WildFly could automatically
add the (supported) Hibernate orm module to the native application, if
the deployment is clearly marked as a Hibernate native application, as
well as also exporting Javassist to the deployment.

Thoughts?

Scott



On Fri, Oct 28, 2016 at 9:44 AM, Scott Marlow <smarlow at redhat.com> wrote:
>>> Right, Hibernate ORM's module should be the one exposing it, not the
>>> application nor JipiJapa.
>>
>> JipiJapa has zero to do with this, we will create a pr later today to
>> remove the unneeded dependencies, which has nothing to do with this
>> conversation.
>
> https://github.com/wildfly/wildfly/pull/9305 is for removing the
> unused Javassist dependency from JipiJapa.  Also removed a few other
> unused dependencies.