Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jakarta EE 10 support #3224

Open
Bozzzo opened this issue Mar 21, 2025 · 0 comments
Open

Jakarta EE 10 support #3224

Bozzzo opened this issue Mar 21, 2025 · 0 comments

Comments

@Bozzzo
Copy link

Bozzzo commented Mar 21, 2025

Bug Report

io.lettuce lettuce-core-6.5.5.RELEASE
is using some "javax.enterprise..." (EE 8) namespaces
that are incompatible with jakarta (EE 10) containers

Environment

  • Lettuce version(s): lettuce-core-6.5.5.RELEASE
  • EE 10 container (like Tomcat 10)

Possible Solution

Modify you build system to publish a transformed artifact with "jakarta" classifier along with normal artifact.

Additional information

My aplication migrated to EE 10 was failing to access redis content.

I could work around by producing in my local maven repository a transformed
"lettuce-core-6.5.5.RELEASE-jakarta.jar"

This can be done with the help of an extra pom.xml ( using org.eclipse.transformer:transformer-maven-plugin ).

Now my main module can consume EE 10 compatible variant by simply adding the dependency a
<classifier>jakarta</classifier>
This fixed my application that can now access redis again.

This work around is however quite cumbersome and requires that the extra transformer pom.xml is tightly coupled with original source pom.xml it would be much better if this transformation was done once for all by publisher itself.

Best regards,
Eager consumer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants