Open
Conversation
Author
|
Any news on this? Is there any chance that this gets merged? |
Member
|
Hi @fabianfrz, the JCache standard and its RI is in maintenance mode and "dormant". As you write yourself:
The RI is Apache licensed. Why you don't fork it and publish the changes under your own group and artefact? |
Author
|
I did not know that it is in maintenance mode so I did not know if I need to have a fork. In that case thanks for clarification. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
use Jakarta EE 10 everywhere except Guice, which does not seem to support it.
Please use a separate branch with separate artifact names or versions for this, since it is incompatible with Java EE 8.
This keeps the old API (javax.cache) and only changes the CDI backend.