[WFCORE-6829] Add a new 'urn:jboss:domain:community:20.0' schema. #6152
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
github-actions
bot
added
the
deps-ok
Also update the SupportedNamespaceParsingTestCases to include stability level tests.
… configurations. Ideally we should be able to run these domain test with the default stability level.
…so version, URI, and Stability are all accessible.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
The CI failures here will need an updated version of Creaper in WildFly to be able to interpret the new namespace URI: |
This was referenced Sep 5, 2024
Closed
|
/retest |
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.
Also update the SupportedNamespaceParsingTestCases to include stability level tests.
https://issues.redhat.com/browse/WFCORE-6829
I will close after CI and submit along with the PR that adds new attributes, first I want to check if there are any unintended consequences across the wider testsuites - a simple local build passes fine.