Community
Participate
Working Groups
When location arguments contain spaces, some tools don't work properly. For example, create a project in your workspace named "Test Project" (the space is important). Create a file "abc.txt" in the project. Create a simple tool with location c:\windows\write.exe and with the argument ${resource_loc}. Select the file abc.txt, then run the tool. Write will try to find the file <workspace location>/Test and fail.
This is pretty important. I think the different Runtime.exec methods handle arguments with spaces differently. If I remember correctly, the ones which take an array of strings work better than the ones which take a single string. Might have to quote args with spaces ourselves.
Need to ensure we also handle user-specified quotes properly.
*** Bug 19515 has been marked as a duplicate of this bug. ***
Code changes done by Ryan. Checked by Simon and Tod
Verified in build 20020610.
