Lock compatibility suite executes during mvn test

Current naming of lock compatibility suite implementations makes them invisible to surefire and failsafe. This commit makes community and forseti tests run during test phase.
neo4j · Mar 3, 2016 · b074fad · b074fad
1 parent d751758
commit b074fad
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/...ommunity/CommunityLocksCompatibility.java → ...locking/community/CommunityLocksTest.java b/...ommunity/CommunityLocksCompatibility.java → ...locking/community/CommunityLocksTest.java
@@ -22,7 +22,7 @@
 import org.neo4j.kernel.impl.locking.LockingCompatibilityTestSuite;
 import org.neo4j.kernel.impl.locking.Locks;
 
-public class CommunityLocksCompatibility extends LockingCompatibilityTestSuite
+public class CommunityLocksTest extends LockingCompatibilityTestSuite
 {
     @Override
     protected Locks createLockManager()

diff --git a/...ck/forseti/ForsetiLocksCompatibility.java → ...rprise/lock/forseti/ForsetiLocksTest.java b/...ck/forseti/ForsetiLocksCompatibility.java → ...rprise/lock/forseti/ForsetiLocksTest.java
@@ -23,11 +23,11 @@
 import org.neo4j.kernel.impl.locking.Locks;
 import org.neo4j.kernel.impl.locking.ResourceTypes;
 
-public class ForsetiLocksCompatibility extends LockingCompatibilityTestSuite
+public class ForsetiLocksTest extends LockingCompatibilityTestSuite
 {
     @Override
     protected Locks createLockManager()
     {
-        return new ForsetiLockManager( ResourceTypes.values());
+        return new ForsetiLockManager( ResourceTypes.values() );
     }
 }