You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having multiple modules on the classpath (Spring Data JDBC and Spring Data JPA) does not cause Spring Data JDBC back off from repositories that it should not implement. This is, because JdbcRepositoryConfigExtension does not declare identifying repository types and annotations.
We should also aid strict configuration mode detection by introducing spring.factories with an entry for org.springframework.data.repository.core.support.RepositoryFactorySupport.
Affects: 1.1 GA (Moore), 1.0.12 (Lovelace SR12), 2.0 M1 (Neumann)
Mark Paluch opened DATAJDBC-437 and commented
Having multiple modules on the classpath (Spring Data JDBC and Spring Data JPA) does not cause Spring Data JDBC back off from repositories that it should not implement. This is, because
JdbcRepositoryConfigExtension
does not declare identifying repository types and annotations.We should also aid strict configuration mode detection by introducing
spring.factories
with an entry fororg.springframework.data.repository.core.support.RepositoryFactorySupport
.Affects: 1.1 GA (Moore), 1.0.12 (Lovelace SR12), 2.0 M1 (Neumann)
Reference URL: spring-projects/spring-boot#18721
Issue Links:
Referenced from: pull request #177
Backported to: 1.1.1 (Moore SR1), 1.0.12 (Lovelace SR12)
The text was updated successfully, but these errors were encountered: