Re: [exec] Executed command can't open file argument

2018-05-03 Thread Mark Trolley
On Thu, May 3, 2018 at 4:34 PM, sebb <seb...@gmail.com> wrote: > On 3 May 2018 at 17:18, Mark Trolley <marktrol...@gmail.com> wrote: > It may be that quotes are being added to the parameter - I assume the > file name does not have quotes. > > Quoting is necessary for p

Re: [exec] Executed command can't open file argument

2018-05-03 Thread Mark Trolley
I'm not sure how to respond to my own thread so I am hoping sending a reply to my own sent message will do it. I experimented and discovered the problem is in the spaces in the filename argument. If the file is renamed to not have spaces the execution succeeds. However, this doesn't work for my

[exec] Executed command can't open file argument

2018-05-01 Thread Mark Trolley
(Sorry if this message appears twice. I sent it once before subscribing and haven't seen it appear in the archives so I assume it wasn't accepted.) I’m trying to use Apache Commons Exec to run the AtomicParsley tagging program, but execution fails with an error that the input file doesn’t exist.