Module not exposing any entity identifying annotations claims all repositories [DATACMNS-1596]

[spring-projects-issues]

Oliver Drotbohm opened DATACMNS-1596 and commented

With multiple Spring Data modules in place the configuration infrastructure consults each module and calls RepositoryConfigurationExtensionSupport.isStrictRepositoryCandidate(…). That in turn returns true if the collection of identifying annotations is empty, which is the default implementation. That results in a Spring Data module not actively implemented to support the strict configuration mode to claim all repositories resulting e.g. in bean definition override errors in Spring Boot

---

Affects: 1.13.23 (Ingalls SR23), 2.1.11 (Lovelace SR11), 2.2 GA (Moore)

Reference URL: spring-projects/spring-boot#18721

Issue Links:

• DATAJDBC-437 Spring Data JDBC does not consider properly strict configuration mode

Referenced from: pull request #411

Backported to: 2.2.1 (Moore SR1), 2.1.12 (Lovelace SR12)