Fail the build instead of skipping Hibernate ORM bytecode enhancement when it's unsupported

Author: yrodiere

extensions/hibernate-orm/deployment/src/main/java/io/quarkus/hibernate/orm/deployment/integration/QuarkusEnhancementContext.java

@@ -2,6 +2,7 @@
 
 import org.hibernate.bytecode.enhance.spi.DefaultEnhancementContext;
 import org.hibernate.bytecode.enhance.spi.UnloadedField;
+import org.hibernate.bytecode.enhance.spi.UnsupportedEnhancementStrategy;
 
 public final class QuarkusEnhancementContext extends DefaultEnhancementContext {
 
@@ -26,4 +27,15 @@ public ClassLoader getLoadingClassLoader() {
         throw new IllegalStateException("The Classloader of the EnhancementContext should not be used");
     }
 
+    @Override
+    public UnsupportedEnhancementStrategy getUnsupportedEnhancementStrategy() {
+        // We expect model classes to be enhanced.
+        // Lack of enhancement could lead to many problems,
+        // from bad performance, to Quarkus-specific optimizations causing errors/data loss,
+        // to incorrect generated bytecode (references to non-existing methods).
+        // If something prevents enhancement, it's just safer to have Hibernate ORM's enhancer fail
+        // with a clear error message pointing to the application class that needs to be fixed.
+        return UnsupportedEnhancementStrategy.FAIL;
+    }
+
 }