Slide, Yes, that would do pretty much what I needed, if I weren't needing to run this on a Win-7 x64 box which doesn't have command.com on it. In any event, since my original email, we've decided that since it's a "bad thing" to have spaces in project names (especially when we're multi-os), that it will just be a requirement that projects which use this legacy tool can't have spaces in their project names, so the workspaces will not have spaces in them either.
Thanks to everyone for their contributions to this topic. Scott On Tue, Jan 22, 2013 at 10:22 AM, Slide <slide.o....@gmail.com> wrote: > Is [1] what you are looking for? > > slide > > 1 - > http://www.andypemberton.com/engineering/windows-short-file-name-shortpath-in-ant-task/ > > > On Tue, Jan 22, 2013 at 9:19 AM, JonathanRRogers < > jonathanrrog...@gmail.com> wrote: > >> On Tuesday, January 22, 2013 10:54:40 AM UTC-5, SA Evans wrote: >>> >>> Within my ant build script, I have a legacy program that is failing >>> because the workspace name has a space in it, and so it's failing as the >>> whole path isn't getting passed in as an argument to this program. It >>> really isn't a solution at this time to change the project name to one >>> without spaces, so I'm wondering if anyone has any quick/dirty suggestions >>> on how to convert, within Ant, a path which has spaces in it into an 8.3 >>> type path. >>> >>> >> This is most likely a problem related to insufficient quoting of a >> command or path. I doubt an "8.3 type path" is really what you need. >> > > > > -- > Website: http://earl-of-code.com >
