rement for the JDK version on which ANT will run?
Best regards,
Davy Toch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Can you show the error that is logged when you run the tests with
forkmode="once"? Is it an OOM (OutOfMemory)?
Paul Taylor schreef:
Hi
If I run my junit tasks from within ant using forkmode="once" a few of
the tests fail - if I remove the forkmode="once" option they work. I
cant really under
nt instead :-).
As a sidenote: if at the end of the failed command line you see a special
character like:
...QUITY-TRUNK\src\ö
then it's almost always related to shell environment size limitations.
Best regards,
Davy Toch
edward pedersson schreef:
Hi
I am using Ant version 1.6.5 and I am
Is this normal ANT behaviour, or should this be considered a bug
for which I should open a bug report?
Btw, I got this behaviour on ANT 1.6.5 and 1.7.0.
Best regards,
Davy Toch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
Improved version (using ant-contrib). I suppose we'll have to wait for
ANT 1.7 in order to have a 100% solution for scoped variables.
build.xml :
]>
&test-uid;.test : ${&test-uid;.test}
macrodef.xml:
]>
¯odef1-uid;.test :
Just wanted to share our (temporary) solution we currently use to have
scoped variables in macrodefs. Not ideal, but it currently works.
build.xml:
]>
&uid;.test : ${&uid;.test}
macrodef.xml
]>
&uid;.test : ${&uid;.test}
--
