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
{{ message }}
This repository has been archived by the owner on Jul 6, 2023. It is now read-only.
Cause a error
"You have defined query method in the repository but you don't have no query lookupstrategy defined.
The infrastructure apparently does not support query methods!"
Down grading to below resolved the issues and looks to be working.
implementation('org.springframework.data:spring-data-commons:2.0.8.RELEASE')
Would recommend using the spring cloud bom to help manage the versions
(Gradle Config)
dependencyManagement {
imports {
mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
}
}
The text was updated successfully, but these errors were encountered:
StephenDillon
changed the title
Spring Version Incompavility
Spring Version Incompatibility
Dec 4, 2018
I got past it by downgrading the dependency above, but later upon deployment to pivotal cloud foundry, it just hangs on startup without any errors or debugging at all, except a mismatch between client and server version.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
springBootVersion = '2.1.0.RELEASE'
springCloudVersion = 'Greenwich.M2'
compile('com.orientechnologies:spring-data-orientdb-object:0.14-3.0.5-SNAPSHOT')
Cause a error
"You have defined query method in the repository but you don't have no query lookupstrategy defined.
The infrastructure apparently does not support query methods!"
Down grading to below resolved the issues and looks to be working.
implementation('org.springframework.data:spring-data-commons:2.0.8.RELEASE')
Would recommend using the spring cloud bom to help manage the versions
(Gradle Config)
dependencyManagement {
imports {
mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
}
}
The text was updated successfully, but these errors were encountered: