-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolves#236 Update the namespace detection for the root namespace to support stability level qualifiers. #237
Conversation
FYI this is the WildFly Core PR that exposed this issue: |
413c216
to
f82132c
Compare
… support stability level qualifiers.
core/src/main/java/org/wildfly/extras/creaper/core/offline/OfflineServerVersion.java
Outdated
Show resolved
Hide resolved
core/src/main/java/org/wildfly/extras/creaper/core/offline/OfflineServerVersion.java
Outdated
Show resolved
Hide resolved
@@ -296,6 +317,23 @@ public void discoverHostXml_wfly28() throws IOException { | |||
test(ServerVersion.VERSION_21_0_0, HOST_XML, WFLY28_ROOT, EAP7_LOGGING, EAP8_EE); | |||
} | |||
|
|||
@Test | |||
public void discoverHostXml_wfly34_community() throws IOException { | |||
test(ServerVersion.VERSION_20_0_0, HOST_XML, COMMUNITY, WFLY27_ROOT, EAP7_LOGGING, EAP8_EE); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just note: the version of root element does not correspond to the test target but we will be updating supported WF versions in next PR so we might fix it there later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 there is no guarantee that the schema version will even be updated on a major WildFly version so many WildFly versions will share the same schema version even if they have distinct model versions.
…lineServerVersion.java Co-authored-by: jbliznak <[email protected]>
…lineServerVersion.java Co-authored-by: jbliznak <[email protected]>
@jbliznak Thank you for the suggestions, I committed them to the topic branch. |
Thank You! |
Within the regular expression I did first try an extra segment of lowercase alpha characters followed by the colon but that is where I saw we had an overlap with the namespaces of some of our early subsystems so instead specify the known qualifiers.
Although they are not all in use at the moment and which one is present by default will change over time I added tests for all stability levels to check they can all be parsed correctly.