Bug 926002

Summary: EAP 6.1 is not using the most up to date schemas for all subsystems
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Stuart Douglas <sdouglas>
Component: BuildAssignee: Stuart Douglas <sdouglas>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: brian.stansberry, pkremens
Target Milestone: ER5   
Target Release: EAP 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stuart Douglas 2013-03-23 06:46:14 UTC
The standard configs are not using the most up to date version of all schemas

Comment 1 Brian Stansberry 2013-03-24 12:27:00 UTC
The effect of this is when the user modifies their config via a management action, the config file will be updated to use all the latest config schema namespaces. This will result in changes to the config file unrelated to the management update, which isn't a failure, but is untidy.

Comment 2 Brian Stansberry 2013-03-24 12:27:50 UTC
https://github.com/jbossas/jboss-eap/pull/72

Comment 3 JBoss JIRA Server 2013-03-25 21:07:18 UTC
Stuart Douglas <stuart.w.douglas> updated the status of jira AS7-6780 to Resolved

Comment 5 Petr Kremensky 2013-04-30 08:00:55 UTC
Verified on EAP 6.1 ER5. All subsystems are using the most up to date schemas.