I logged the following issue on Spring Boot issue tracker and have now been directed here.
Spring-Boot 2.0.8 adds the mappings by creating entities from the *hbm.xml files listed in spring.jpa.mapping-resources=hibernate.cfg.xml, Any release after that ignores the mapping file.
Previously this was no problem at all.
In our project there just is no difference between the mapped classes and the annotated @Entity classes. Why should there be a difference?
Sure… in a perfect world where i have time to figure out all the Hibernate internals. In the meantime i’ll stick to that release until i can squeeze it no further.
I surely understand what you mean since we also don’t have the resources to fix all the issues and since HBM mappings are considered deprecated, this issue does not have a high priority.
Hi Vlad, (maybe somewhat late but) if HBM mappings are considered deprecated, is the only mapping then the annotations or is there a non deprecated way to externalize entity mappings? We just wanted to use those external mappings in our Spring Boot apps. I also don’t find any notion in the docs for it considered deprecated. (We didn’t try any yet because of this post)