Author: steve.ebersole(a)jboss.com
Date: 2007-12-07 17:47:01 -0500 (Fri, 07 Dec 2007)
New Revision: 14237
Modified:
core/trunk/cache-jbosscache2/pom.xml
Log:
handle jgroups.bind_addr set from the maven command line
Modified: core/trunk/cache-jbosscache2/pom.xml
===================================================================
--- core/trunk/cache-jbosscache2/pom.xml 2007-12-07 22:45:41 UTC (rev 14236)
+++ core/trunk/cache-jbosscache2/pom.xml 2007-12-07 22:47:01 UTC (rev 14237)
@@ -126,16 +126,14 @@
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<systemProperties>
- <!-- If you find the testsuite runs very slowly, there
- may be problems with multicast on the interface
- JGroups uses by default. You can try to resolve
- this by uncommenting this property and setting the
- value to an interface where you know multicast works
<property>
+
<name>hibernate.test.validatefailureexpected</name>
+ <value>true</value>
+ </property>
+ <property>
<name>jgroups.bind_addr</name>
- <value>192.168.0.1</value>
+ <value>${jgroups.bind_addr}</value>
</property>
- -->
<!-- There are problems with multicast and IPv6 on some
OS/JDK combos, so we tell Java to use IPv4. If you
have problems with multicast when running the tests
@@ -155,6 +153,13 @@
<properties>
<skipUnitTests>true</skipUnitTests>
+ <!--
+ Following is the default jgroups mcast address. If you find the testsuite
runs very slowly, there
+ may be problems with multicast on the interface JGroups uses by default on
your machine. You can
+ try to resolve setting 'jgroups.bind_addr' as a system-property to
the jvm launching maven and
+ setting the value to an interface where you know multicast works
+ -->
+ <jgroups.bind_addr>127.0.0.1</jgroups.bind_addr>
</properties>
<profiles>