Adjust wording of specification and API around @Priority usage on ste…#531
Merged
manovotn merged 1 commit intojakartaee:masterfrom Sep 21, 2021
Merged
Conversation
Ladicek
reviewed
Sep 21, 2021
manovotn
force-pushed
the
adjustPriorityWording
branch
from
79294f2 to
7f0961b
Compare
Ladicek
approved these changes
Sep 21, 2021
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
2 participants
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.
…reotypes.
Follow up on #524
This PR aligns the wording closely to what spec already uses. Instead of specifically listing options, it simply allows usage of this stereotype on beans.