Bug 1028474 - Pull jboss-as-infinispan_1_4.xsd changes from WildFly into EAP
Summary: Pull jboss-as-infinispan_1_4.xsd changes from WildFly into EAP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Clustering
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.2.0
Assignee: Paul Ferraro
QA Contact: Jitka Kozana
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-08 14:26 UTC by Darran Lofthouse
Modified: 2013-12-15 16:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:20:38 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-2471 0 Major Closed jboss-as-infinispan_1_4.xsd differs between EAP and WildFly 2015-08-12 14:39:51 UTC

Description Darran Lofthouse 2013-11-08 14:26:36 UTC 
Description of problem:

The schema has been cleaned up within WildFly, the same changes should be pulled into EAP so that there is only one version 1.4.

(Not a blocker for a release but we do need to be able to verify schema compatibility, the current differences make this difficult)
Comment 2 Brian Stansberry 2013-11-08 15:54:09 UTC 
This absolutely should be a blocker; we cannot have two different versions of this schema in .Final releases.

It's no big deal to fix this; the PR is there already.
Comment 3 Paul Ferraro 2013-11-08 16:01:37 UTC 
Just to say, the versions are equivalent and any changes are cosmetic only.  So, I wouldn't call this a blocker - although it is inconvenient.

https://github.com/jbossas/jboss-eap/pull/684

I'll add a link to this BZ to the PR.
Comment 4 Brian Stansberry 2013-11-08 16:09:09 UTC 
Blocker, not blocker, whatever. It has to be fixed because it's absolutely stupid not to. :)
Comment 6 Jitka Kozana 2013-11-11 11:45:02 UTC 
This issue was verified using the 6.2.0.CR1 preview bits.
Note You need to log in before you can comment on or make changes to this bug.