Include jakarta.annotation-api in BOM #1035
Merged
Conversation
This file contains 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
dmatej
approved these changes
May 20, 2024
|
However Annotation 3.0 is for Jakarta EE 11, right? Then it should go rather to 4.0.0-prepare branch. Or we could merge that branch to master and create 3.x branch from the last commit before. |
Hmmm... This change in BOM only follows what is set in parent already.
Perhaps preparation could be finalized and merged to master.
This will not work then as the said annotation-api is bumped in master already. But some commit before, like edb7a0b could do. |
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.
No description provided.