Hi, I took a look at the bytecode enhancement Maven plugin and I also have this issue https://hibernate.atlassian.net/browse/HHH-8833 . As far as I can tell the Maven plugin (and I suppose the Gradle plugin too) doesn't provide any information about the classpath so it's impossible to use the bytecode enhancement plugin in real life applications because you obviously have dependencies to other classes. Is this something supported or something very experimental? I found some old posts of Emmanuel discouraging the use of bytecode enhancement so I'm not sure it's a good idea to invest our time in it? Basically, we have a lot of nullable @OneToOne properties and as far as I understood it, it's supposed to help this case a lot. Maybe using something like http://www.mograblog.com/2010/01/setting-classloader-in-maven-plugin.html might be a good idea for the Maven plugin? Anyway feedback welcome before we invest time in it. Thanks. -- Guillaume _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

On Mar 19, 2014, at 19:09, Guillaume Smet <guillaume.smet(a)gmail.com&gt; wrote: On Wed, Mar 19, 2014 at 6:06 PM, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > My comment about bytecode enhancement was at a time where Hibernate ORM > did not make as much optimizations as it does now. > In an ideal world, the bytecode enhancement is triggered at startup time > like we do for Java EE. I am not sure if that's doable in your > environment though. We are in a Tomcat + Spring environment so I don't think it's doable and we have to stick to compile time enhancement. I'll see if we can commit some time to put the Maven plugin in shape. -- Guillaume _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev