Jakarta REST 4.0 Epic: Updating top-level files #1171
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
andymc12
approved these changes
Aug 14, 2023
chkal
approved these changes
Aug 14, 2023
|
Maybe this should be a separate job or we should disable Java 11 testing since Jakarta REST 4.0 currently requires Java 17. |
Java 11 was disabled by separate PR. |
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.
This issue resolved the item "Update README, LICENSE and review all other top-level files" from the Jakarta REST 4.0 Epic.
In fact, all top-level files look good and do not need any changes justified by switching from 3.1 to 4.0 (some other changes might be useful but should go into
master, or are covered by other PRs already).The sole change is the correction of the used branch name.