Today, lettuce is heading towards the fifth major release with Reactive Streams support based on Project Reactor, dynamic command interfaces to integrate with Redis Modules and has a broad user base. Therefore, Lettuce gets its own domain lettuce.io, Twitter handle @LettuceDriver, and Github organization github.com/lettuce-io/. Beginning with Lettuce 5, the GroupId/ArtifactID and package names are relocated to io.lettuce:lettuce-core, respective io.lettuce.core. Lettuce distributions will come with a reference guide that originates in the Lettuce Wiki, and it received a beautiful logo to define Lettuce’s personality so you can continue to build elastic data access with Redis.

If it happens that you meet me at a conference such as JavaLand, ask me for Lettuce stickers.

As a Developer, What do I need to know?

Two things change for you:

  1. Use a different GroupId and ArtifactId for versions beginning as of 5.0:

Old

<dependency>
  <groupId>biz.paluch.redis</groupId>
  <artifactId>lettuce</artifactId>
  <version>(3|4).y.z</version>
</dependency>

New

<dependency>
  <groupId>io.lettuce</groupId>
  <artifactId>lettuce-core</artifactId>
  <version>5.y.z</version>
</dependency>
  1. Replace com.lambdaworks.redis with io.lettuce.core in your imports and logging config files.
  2. There’s no 3., that’s it!

With 5.0, the version numbering scheme changes slightly. Snapshots are published as 5.0.0.BUILD-SNAPSHOT, milestones as 5.0.0.M1/5.0.0.RC1 and releases as 5.0.0.RELEASE.

All links to redis.paluch.biz are rewritten to lettuce.io so don’t worry if you have links set to the documentation available from redis.paluch.biz, these links will redirect to the corresponding location on the new site.

TL;DR