Unfortunately, that doesn't work either. When I do this:
The result is:
BUILD FAILED
E:\eclipse\3.1.1\eclipse\workspace\Resume_JDK_1.5.0\xml\word.xml:40: Execute
failed: java.io.IOException: CreateProcess: "C:\Documents and
Settings\Rhino\My Documents\LaunchWdMacro.vbs" Fred Flintston
I just remembered something about the exec task:
On Windows, the Execute class, used by the ExecTask,
itself launches cmd.exe to handle the command.
You might try executable="${vbs.script}"
On Jan 28, 2006, at 7:35 PM, Rhino wrote:
I tried adding resolveExecutable="true" and it made no differe
I tried adding resolveExecutable="true" and it made no difference.
What do you mean when you say to use an absolute path? I am already using
one in the 'vbs.script' property so I added the absolute path to 'cmd.exe'.
This made no difference either; the task still has no errors but the name
did
Use the exec attribute resolveExecutable="true",
or use an absolute path.
On Jan 28, 2006, at 5:55 PM, Rhino wrote:
I'm having a bit of trouble with an exec task in Windows XP
Professional and I would appreciate a bit of help from the experts
on this mailing list.
I have created a short VBS
I'm having a bit of trouble with an exec task in Windows XP Professional and
I would appreciate a bit of help from the experts on this mailing list.
I have created a short VBScript that invokes a Microsoft Word macro; the
macro expects exactly two parameters on the command line and adds the val
On Fri, 27 Jan 2006, Carlton Brown <[EMAIL PROTECTED]>
wrote:
> The ant task seems to create zero-length output files for a
> few of my unit test classes.
Which version of Ant are you using? There have been some problems
with tests running into timeouts or crashing the VM, but they are
supposed
