Skip to content
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

ISPN-6342 Fix ConfigurationUnitTest #4095

Conversation

slaskawi
Copy link
Contributor

@slaskawi slaskawi commented Mar 9, 2016

@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
version="1.0" targetNamespace="urn:infinispan:config:8.2"
xmlns:tns="urn:infinispan:config:8.2" xmlns:xs="http://www.w3.org/2001/XMLSchema">
version="1.0" targetNamespace="urn:infinispan:config:9.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confused as to how this would fix a test. We haven't branched yet so we shouldn't be adding 9.0 changes yet afaik.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wburns The version number in master is 9.0.0-SNAPSHOT, and ConfigurationUnitTest.testSchema() tries to load infinispan-config-<major>.<minor>.xsd. So we probably don't need the namespace changes yet, but we need the new schema file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like we need to branch then :) Unless we aren't going to do anything more for 8.2.

@wburns wburns added the Question label Mar 9, 2016
@@ -1178,7 +1178,7 @@
Must implement `org.infinispan.distribution.ch.KeyPartitioner`.
A custom key partitioner can be used as an alternative to grouping, to guarantee that some keys
are located in the same segment (and thus their primary owner is the same node).
Since 8.2.
Since 9.0.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

8.2 seems fine here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All right... I'll leave it than

@@ -1258,7 +1258,7 @@
Must implement `org.infinispan.distribution.ch.KeyPartitioner`.
A custom key partitioner can be used as an alternative to grouping, to guarantee that some keys
are located in the same segment (and thus their primary owner is the same node).
Since 8.2.
Since 9.0.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can be removed here as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I'll leave it as is

@slaskawi slaskawi force-pushed the ISPN-6342-Fix-ConfigurationUnitTest branch from e501b09 to 86f45a7 Compare March 9, 2016 15:19
@slaskawi
Copy link
Contributor Author

slaskawi commented Mar 9, 2016

Sorry I missed a couple of bits. Now it should be fine.

And we need a new Release Name!!! :D

@danberindei
Copy link
Member

Integrated, thanks Sebastian!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants