Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
spring-projects-issues opened this issue Oct 24, 2019 · 0 comments
Assignees
Labels
in: repository type: bug

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Oct 24, 2019

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: repository type: bug
Projects
None yet
Development

No branches or pull requests

2 participants