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
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: