first step toward using standard MPConfig property names #7794
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.
In order to align with standards being defined for MicroProfile specs that define their own MicroProfile Config properties, we need to change the name of 7 properties that MicroProfile Context Propagation uses to supply default values for ManagedExecutor/ThreadContext instances. Per eclipse/microprofile#100 these property names should be prefixed with mp.[spec-name]. and per eclipse/microprofile-config#420 these property names should avoid the use of /.
This pull will make OpenLiberty tolerate either form of the property names for now. Then, once the spec changes goes through, we can remove support for the old names.