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
We've been using cache-redis plugin with spring cache annotations on Grails 2.3.7, but want to upgrade to this plugin, but can't due to dependency issues, wanted to reach out before we dumped our legacy code and started fresh. Due to code dependencies, we can't remove cache-redis without breaking a LOT of code, so we want to leverage redis plugin incrementally until later when we can drop cache-redis entirely.
But this causes error when refreshing/compiling dependencies,
| Environment set to development.....
| Error Fatal error during compilation org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
C:\PROJECTS\WorkspaceSTS2\kennis-cache-plugin-AUG2014\target\work\plugins\redis-1.5.5\.\RedisGrailsPlugin.groovy: 20: unable to resolve class redis.clients.jedis.JedisSentinelPool
@ line 20, column 1.
import redis.clients.jedis.JedisSentinelPool
Since redis plugin uses a newer version of jedis, 2.4.2, we excluding jedis from cache-redis,
We've been using
cache-redis
plugin with spring cache annotations on Grails 2.3.7, but want to upgrade to this plugin, but can't due to dependency issues, wanted to reach out before we dumped our legacy code and started fresh. Due to code dependencies, we can't remove cache-redis without breaking a LOT of code, so we want to leverage redis plugin incrementally until later when we can drop cache-redis entirely.Current BuildConfig:
BuildConfig with redis:1.5.5,
But this causes error when refreshing/compiling dependencies,
Since redis plugin uses a newer version of jedis, 2.4.2, we excluding jedis from cache-redis,
We managed to eliminate the compilation error, but on startup, we're getting the following error:
No surprise, really, since we configure connections in cache-redis, so we're stuck.
Is it possible to make cache-redis:1.0.0 and redis:1.5.5 play nice together on 2.3.7, or are we wasting our time?
The text was updated successfully, but these errors were encountered: