Always use conf/hazelcast.default.xml during mvn test
After this patch, users should not be forced to update hazelcast.xml
just for running unit tests.
- If someone ever want to run unit tests using different hazelcast.xml
$ mvn test -DargLine="-D-Dnet.onrc.onos.core.datastore.hazelcast.baseConfig=..."
Change-Id: I6eaec95f2808cb54fd21610821e4f2147ceb95bf
diff --git a/pom.xml b/pom.xml
index 5d06100..d3de578 100644
--- a/pom.xml
+++ b/pom.xml
@@ -60,6 +60,7 @@
<metrics.version>3.0.2</metrics.version>
<maven.surefire.plugin.version>2.16</maven.surefire.plugin.version>
<curator.version>2.6.0</curator.version>
+ <argLine/>
</properties>
<build>
<plugins>
@@ -156,7 +157,7 @@
<configuration>
<!-- FIXME -XX:-UseSplitVerifier added as workaround for JDK 1.7.0u65 + PowerMock issue
https://issues.jboss.org/browse/JASSIST-228 -->
- <argLine>-XX:MaxPermSize=256m -Dhazelcast.logging.type=slf4j -XX:-UseSplitVerifier</argLine>
+ <argLine>-XX:MaxPermSize=256m -Dhazelcast.logging.type=slf4j -XX:-UseSplitVerifier -Dnet.onrc.onos.core.datastore.hazelcast.baseConfig=${project.basedir}/conf/hazelcast.default.xml ${argLine}</argLine>
<redirectTestOutputToFile>false</redirectTestOutputToFile>
<excludedGroups>net.onrc.onos.core.util.IntegrationTest</excludedGroups>
</configuration>