Implement CDI 5.0-M1 features #3251
Merged
Conversation
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
manovotn
force-pushed
the
cdi50M1
branch
7 times, most recently
from
7e71064 to
898614e
Compare
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.
Work in progress towards implementing M1 API as well as re-enabling testing with WFLY.
WFLY testing will require changes to our settings but primarily we need wildfly/wildfly#19360 to get merged and then get a nightly build with it.
EDIT: Test coverage for this is present in the CDI TCKs, namely its already part of the M1 artifact which this PR uses. Passing the CI therefore means we also pass the TCK coverage.