[hibernate-dev] How best to eliminate the Javassist dependency from Hibernate applications...
smarlow at redhat.com
Tue Feb 16 14:07:28 EST 2016
https://hibernate.atlassian.net/browse/HHH-10536 is for tracking this.
Please revise as it makes sense.
In the related WildFly dev discussion about $subject, Stuart asked if we
would have two separate Hibernate ORM jars (one that depends on the
shaded Javassist and one that depends on regular Javassist). That seems
like a separate concern but perhaps others will feel stronger about it.
Also, in the WildFly discussion, I asked whether it makes a difference
to Hibernate, whether the javassist.util.proxy classes that we want to
shade, are in the javassist.jar or a new javassist-runtime.jar? If we
shade all of the classes in a javassist-runtime.jar, that might be a
better long term contract, then if we shaded the javassist.util.proxy
classes which could be renamed over time. Does it make a difference
whether we shade the javassist.util.proxy or entire javassist-runtime.jar?
More information about the hibernate-dev