-
Notifications
You must be signed in to change notification settings - Fork 464
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
Add ModelTestControllerVersion for XP 4 #4899
Conversation
// EAP_XP_4("4.0.0.GA-redhat-0000x", true, "23.0.0", "18.0.0.Final-redhat-0000x", "xp4") | ||
// We will also need to remove the *-wf26 files in wildfly-legacy-test and replace them with *-xp4 ones | ||
// generated from EAP 7.4.0 with XP 4 installed | ||
EAP_XP_4("26.0.0.Beta1", false, "25.0.0", "18.0.0.Final", "wf26") |
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.
It should be fine, although I don't understand at all why you added the WF Model descriptions for WF26 (wildfly/wildfly-legacy-test@ffab0be), indeed using a Beta1 release instead of a Final, and then you added the legacy controllers for WF25 (wildfly/wildfly-legacy-test@b214f32)
Probably they are the same but seems a bit misleading since we are getting here an enum that uses WF26 with WF25 controllers.
@kabir Is this configuration expected by you?
I would expect to have WF26 model descriptions based on a Final release on wildfly-legacy-test and WF26 subsystems and controllers instead of WF25, but I'm not sure about the intentions behind this.
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.
Hi @yersan, there are a few parts to this:
- 26.0.0.Beta1 and 18.0.0.Final are the versions which will be used at runtime by the legacy controllers.
- 25.0.0 is the version of the legacy controller adapters to use (i.e. the subfolder in wildfly-legacy-test under core/ and subsystem/). These are compiled against a version of the controller API, but really the versions above specify what is pulled in for the legacy controller at runtime.
We introduce these adapters when there is a breaking change. In this case the breaking change was introduced with WildFly 25.0.0 where the VaultReader was removed from various server module APIs used by these server adapters.
I agree it is slightly confusing, but in the (very unlikely) case we would need transformers tests for WildFly 25 at some stage we can reuse the "25.0.0" versions. And if there are no breaking changes in the next few controller versions, we would be able to use an enum like the following for that:
FUTURE_RELEASE("28.0.0.Final", false, "25.0.0", "20.0.0.Final", "wf28")
So IMO it is correct.
Although, I see I have a typo on the following line:
// EAP_XP_4("4.0.0.GA-redhat-0000x", true, "23.0.0", "18.0.0.Final-redhat-0000x", "xp4")
Here "23.0.0" should be "25.0.0", I'll replace that.
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.
Or to put it another way, if the VaultReader had not been removed from the server in WildFly 25, we could have continued using the "23.0.0" adapters used in the previous EAP_7_4_0 version :-)
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.
Ok, I understand. It was more natural to me to think more about even versions that belong all to the referred legacy version.
This legacy test framework still has a lot of unknown details to me, so I only commented on what I saw weirdly. If you are fine with the changes on wildfly-legacy-test
and how they are brought in, I'm fine too.
559d9ce
to
bb6923f
Compare
Core - Full Integration Build 11290 outcome was FAILURE using a merge of bb6923f Failed tests
|
@kabir thanks |
https://issues.redhat.com/browse/WFCORE-5751
https://issues.redhat.com/browse/WFCORE-5752