RepositoryBeanNameGenerator fails to resolve bean names for custom implementations detected via Spring's component index [DATACMNS-1115] #1558
Comments
Oliver Drotbohm commented Just for reference: this problem doesn't occur with a simple upgrade. The culprit here is the addition of the indexer. I've patched |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Juergen Zimmermann opened DATACMNS-1115 and commented
After upgrading to Spring Boot 2.0.0.M2 and Spring Data Kay.M4 I cannot start my microservices any more which are accessing MongoDB. A testcase is appended to produce the stacktrace below.
First I thought it is a Spring Boot issue spring-projects/spring-boot#9780
Stacktrace:
Affects: 2.0 M4 (Kay)
Attachments:
Backported to: 1.13.5 (Ingalls SR5), 1.12.12 (Hopper SR12)
The text was updated successfully, but these errors were encountered: