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
https://issues.jboss.org/browse/WFLY-2914 add cli xsd version 1.3 which ... #5905
Conversation
Build 2651 is now running using a merge of d613127 |
Build 2651 outcome was SUCCESS using a merge of d613127 |
This shouldn't be merged until master is opened for 9.x. This should go in 9.x as 8.0.1.Final will be produced before any EAP GA release that has this schema in it. If we put 1.3 in a WF .Final and then there needs to be some change in EAP 6.3, EAP will have to move to 1.4. |
@bstansberry wdyt about this one still. We are already bumping config versions should we let this one in? |
No, the rationale for not including this is once it's in a .Final release, that number is burned and any further changes needed in EAP 6.3 (which is where 1.3 first appears) will require a version bump. There's no need for 1.3 in 8.0.1 because 2.0 already has the relevant config items. @aloubyansky is there any difference between this 1.3 and what's currently in 2.0? |
Yes, new configuration elements related to protocol and named controllers (Darran was working on) and access-control. |
Thanks. I asked because today we realized we had forward ported a 1.x version of another schema that was identical to its 2.0 version. :) |
ok well leave it out then |
Needs a rebase. |
…ch is 1.2 plus vault configuration
Build 3720 is now running using a merge of 335be3b |
Build 3720 outcome was SUCCESS using a merge of 335be3b |
https://issues.jboss.org/browse/WFLY-2914 add cli xsd version 1.3 which ...
...is 1.2 plus vault configuration
Thanks,
Alexey