[jboss-jira] [JBoss JIRA] (WFLY-1936) Ensure RBAC metadata changes result in management API bump
[
https://issues.jboss.org/browse/WFLY-1936?page=com.atlassian.jira.plugin....
]
Brian Stansberry edited comment on WFLY-1936 at 8/24/13 9:05 AM:
-----------------------------------------------------------------
Category 1 +3)
datasources 2.0.0 needs to transform to new 1.2.0
logging 2.0.0 needs to transform to new 1.3.0 (WFLY-1807)
messaging 2.0.0 needs transform to new 1.3.0
modcluster 2.0.0 needs transform to new 1.4.0 (plus already missing transform to 1.3.0 --
WFLY-1938)
naming 2.0.0 needs transform to new 1.3.0
remoting 2.0.0 needs transform to new EAP 1.3.0
resource adapters 2.0.0 needs transform to new 1.3.0
Category 2)
jacorb to 1.3.0 from 1.2.0
jdr to 1.2.0 from 1.1.0
jmx to 1.2.0 from 1.1.0 (requires reverting bump to 2.0.0 which is unneeded since all
changes are going to EAP 6.2)
mail to 1.3.0 from 1.2.0
security to 1.3.0 from 1.2.1
Special cases)
web -- WF got bumped from 1.2.0 to 2.0.0 but none of the WF changes survived the removal
of JBW, so really WF should go to 1.3.0
was (Author: brian.stansberry):
Category 1 +3)
datasources 2.0.0 needs to transform to new 1.2.0
logging 2.0.0 needs to transform to new 1.3.0 (WFLY-1807)
messaging 2.0.0 needs transform to new 1.3.0
modcluster 2.0.0 needs transform to new 1.4.0 (plus already missing transform to 1.3.0 --
WFLY-1938)
naming 2.0.0 needs transform to new 1.3.0
remoting 2.0.0 needs transform to new EAP 1.3.0
Category 2)
jacorb to 1.3.0 from 1.2.0
jdr to 1.2.0 from 1.1.0
jmx to 1.2.0 from 1.1.0 (requires reverting bump to 2.0.0 which is unneeded since all
changes are going to EAP 6.2)
mail to 1.3.0 from 1.2.0
resource adapters to 1.3.0 from 1.2.0
security to 1.3.0 from 1.2.1
Special cases)
web -- WF got bumped from 1.2.0 to 2.0.0 but none of the WF changes survived the removal
of JBW, so really WF should go to 1.3.0
Ensure RBAC metadata changes result in management API bump
----------------------------------------------------------
Key: WFLY-1936
URL: https://issues.jboss.org/browse/WFLY-1936
Project: WildFly
Issue Type: Sub-task
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 8.0.0.CR1
The RBAC metadata counts as a management API change and needs a version bump.
Validate that all subsystems that have had RBAC metadata added:
1) Have already had a management API bump to the next major (because they had some other
change)
2) OR get a minor management API bump to match what we will do in EAP 6.2.
3) For those in category 1), there will be a minor bump on the previous major version in
EAP 6.2. The transformation added in WF 8 needs to cover that version as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira