On Wed, Jul 4, 2018 at 11:46 AM Emmanuel Bernard <emmanuel(a)hibernate.org>
wrote:
Having the create-warn by default and allowing the user to move to
create or fail is a good compromise. Vlad, in the documentation, we can
have a get ready for production section that mention this problem and
many others :)
OK, done.
I like the idea of Guillaume to try and capture all failing cache
creations and return them as a single error. It's not a blocker though
and if that cannot make it in our 5.3 sprint, that is acceptable.
So in the default create-warn case, you obviously have listed all the
caches that are not defined.
It might be nice to do the same thing for the fail case but that is for
another day.
--
Guillaume