| Thanks for your comments Rafael Winterhalter! I agree this is not what I like in the long term, but since it's a minor version we will compromise for sake of compatibility with the previous release - too many problems for end users, the compatibility matrix Spring/Hibernate/others is a non trivial obstacle for many. I'll add the additional '$' for now. For future I'd expect other frameworks to not rely on names at all, I'd rather introduce an explicit stable API for such needs - if we'll get a clear description of such needs. Just curious, why do you mention Scala and Kotlin naming patterns, they won't be affected by Hibernate conventions would they? |