Hi!
It's with great pleasure that I announce you the release of Hibernate
Validator 5.4.0.CR1.
This candidate release brings a few improvements and bugfixes on top of our
Beta1.
For more information, see the announcement post here:
http://in.relation.to/2017/01/12/hibernate-validator-540-cr1-fin
To be clear... ORM is "expecting the application classpath to include
Javassist dependency" because it will need it for the *proxies* Hibernate
returns to be usable once they get them from Hibernate.
It may or may not *need* the application classpath to include Javassist
dependency if the applicat
No, not currently. We created
https://github.com/wildfly/wildfly/pull/8474 to move the exporting of
Javassist, to the WildFly static ORM module, so that Hibernate native
applications would automatically get the Javassist classes. That
wouldn't of directly addressed your situation but it would of
Following Steve's suggestions I thought I had a reasonable and clean
plan, but it's not working in practice.
Turns out that even after me cleaning up all references to
"org.javassist:main", it's still been forced on the classpath by
hard-coded rules in the JPADependencyProcessor, so conflicting wi
