Well, I was hoping they were running Ant 1.7 . Which would have solved one
of our problems...
The only way to get JBehave to run on their cruise box is to run it in
java.awt.headless mode. We could always put this into the build file, but
then we'd always get pending exceptions if we ran the build locally,
rather than actually exercising the behaviours. The right thing to do
seems to me to be: set their box to run Ant headlessly, then pass the Ant
vm's system args on to the behaviour vm.
Is that OK? If CC.rb come back and say 'no way' then I shall remove it
again, but at the moment it's failing the build anyway.
Cheers,
Liz.
Dan North <[EMAIL PROTECTED]> wrote on 12/03/2007 19:28:50:
> Um, why?
>
> [EMAIL PROTECTED] wrote:
> Revision
> 703
> Author
> sirenian
> Date
> 2007-03-12 13:17:44 -0500 (Mon, 12 Mar 2007)
> Log Message
> [EK] Added clonevm property to java behaviour verification target.
> Modified Paths
> trunk/build.xml
> Diff
> Modified: trunk/build.xml (702 => 703)
> --- trunk/build.xml 2007-03-11 05:09:56 UTC (rev 702)
> +++ trunk/build.xml 2007-03-12 18:17:44 UTC (rev 703)
> @@ -104,7 +104,7 @@
> </target>
>
> <target name="verify-behaviour" depends="compile-behaviour"
> description="Verify behaviour">
> - <java taskname="run behaviours" classname="org.jbehave.core.
> Run" fork="true" failonerror="true">
> + <java taskname="run behaviours" classname="org.jbehave.core.
> Run" fork="true" failonerror="true" clonevm="true">
> <arg value="org.jbehave.AllBehaviours" />
> <classpath>
> <pathelement path="${behaviour_classes_dir}" />
>
>
>
> To unsubscribe from this list please visit:
> http://xircles.codehaus.org/manage_email
