Jedis,spring-redis-data integration Use, version problem exception

Jedis,spring-redis-data integration, when the version mismatch, often reported some exceptions, such as
1:java.lang.noclassdeffounderror:org/springframework/data/geo/metric
2:java.lang.nosuchmethoderror:redis.clients.jedis.jediscluster.set ([b[b) ljava/lang/string
3:jedis.exceptions.jedisconnectionexception:unknown Reply:3

are caused by Jedis,spring-redis-data,spring-data-common and other package version matching.

The best solution, with Spring-redis-data package as the center, refers to the matching Jedis or Spring-data-common:

<Dependency>    <groupId>Org.springframework.data</groupId>    <Artifactid>Spring-data-commons</Artifactid>    <version>1.8.4.RELEASE</version></Dependency><!--SPRING-DATA-REDISR -<Dependency>    <groupId>Org.springframework.data</groupId>    <Artifactid>Spring-data-redis</Artifactid>    <version>1.8.4.RELEASE</version></Dependency><Dependency>    <groupId>Redis.clients</groupId>    <Artifactid>Jedis</Artifactid>    <version>2.9.0</version></Dependency>

Jedis,spring-redis-data integration Use, version problem exception