FYI, we changed this behavior for 5.3.2:

• by default, you will have a warning for each cache that is not defined but the bootstrap won't fail
• you can enforce a bootstrap failure using the hibernate.javax.cache.missing_cache_strategy property to fail

We think it's a better compromise for usability. Framework developers can still have the bootstrap failure behavior if they want.