relocation Jedis client package paths to avoid class conflicts
Can you elaborate on what the problem is?
Hi @codemonstur , Since embedded-redis directly references the dependency of the Jedis client, when I use a different version of Jedis during the process, version incompatibility causes embedded-redis to throw a ClassNotFoundException in cluster mode.
Could I introduce the maven-shaded-plugin to shade Jedis into the embedded-redis jar as a replacement for the dependency?
The mechanism you use to include a particular version of Jedis shouldn't matter. Either you include one that works, or you don't.
I can't get rid of Jedis, it is necessary for some functionality. And I don't want to delete that functionality either.
I still don't get what you are trying to do though. Are you trying to replace my version of Jedis with a newer one and it fails? Or are you trying to use an older version and it fails? If you are using an older version; why?