|
The "bug" is about allowing to specify a value for exclude-unlisted-classes when used in SE environments. And no, I don't believe Hibernate never supported that. What it did allow/support in SE environments was to either:
1) not specify exclude-unlisted-classes and have scanning happen
2) specify exclude-unlisted-classes and have scanning not happen regardless of value
So I understand the discussion very well. You just want to argue, imo, as a continuation of your earlier frustration over
HHH-8111
. Really you are arguing that our ignoring the boolean value specified within exclude-unlisted-classes was a bug. I simply pointed out that that is in fact not really true, since the JPA spec specifically says exclude-unlisted-classes is not supposed to be used in SE environments. So this cannot really be a bug.
As Brett said the patch was largely accepted. Up to you if you want to continue to argue...
|
