[
https://issues.jboss.org/browse/WFCORE-22?page=com.atlassian.jira.plugin....
]
Darran Lofthouse moved WFLY-2956 to WFCORE-22:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-22 (was: WFLY-2956)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Alpha4
(was: 9.0.0.CR1)
Port version 1.6 of the management schema upstream.
---------------------------------------------------
Key: WFCORE-22
URL:
https://issues.jboss.org/browse/WFCORE-22
Project: WildFly Core
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 1.0.0.Alpha4
EAP will be introducing version 1.6 of the management schema, this needs porting
upstream.
At the same point the coding convention we have adopted has been based around a linear
progression of the configuration schemas, when version 1.5 was ported this still worked as
1.5 contained a subset of the changes that went into 2.0.
1.6 is going to be a special case as it will build on 1.5 so is already a subset of 2.0
but will also only contain a subset of changes that go into 3.0 - the risk however is our
switch statements are built around dropping into a default block that is hit for all
schema versions not explicitly listed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)