One more thing, here is the template I use to define the sf daemon we
run for our tests
<sf-startdaemon
classpathref="tests.run.classpath"
logStackTraces="true"
spawn="true"
securityManager="${security.manager}"
dir="${build.test.dir}"
timeout="0"
serverHostname="${deploy.server.hostname}"
>
<!-- assertions are enabled -->
<assertions refid="sf.assertions"/>
<jvmarg line="${daemon.jvmargs}"/>
<!-- load in a property file if it is present -->
<propertyfile file="${runtime.properties}" optional="true"/>
<!--copy all proxy settings from the running JVM-->
<syspropertyset refid="proxy.settings"/>
<syspropertyset>
<!--copy all properties beginning with test. or run.-->
<propertyref prefix="test."/>
<propertyref prefix="run."/>
<!--SF core options-->
<propertyref prefix="org.smartfrog.sfcore."/>
<!-- RMI options-->
<propertyref prefix="java.rmi."/>
<!-- Log settings for various tools-->
<propertyref prefix="org.mortbay.log."/>
<propertyref prefix="log4j."/>
<propertyref prefix="org.apache.commons.logging."/>
</syspropertyset>
</sf-startdaemon>
With some predefined properties
<property name="security.manager" value="none"/>
<property name="daemon.jvmargs" value=""/>
<!-- set to 127.0.0.1 for local only deployments -->
<property name="deploy.server.hostname" value="127.0.0.1"/
the 127.0.0.1 url means the service only serves loopback addresses,
which is less troublesome when developing on roaming laptops.
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Smartfrog-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartfrog-users
