Apologies for spamming the list, folks.
I've just realised that it does in fact work. It turns out that because
we haven't installed source control yet, when I tried this it had actually
been using an older version of the properties file, that contains an
invalid path (a non-escaped backslash is p
Update:
Oops. My mistake, no it doesn't :/ Ack, it's going to be one of those
days. I think I'm going to have to go with the progra~1 form then.
Thanks anyway for the help.
Thanks for the reply.
I can't use multiple tags as there's no guarantee that
the classpa
Thanks for the reply.
I can't use multiple tags as there's no guarantee that
the classpath will have a certain number of elements.
However, using one pathelement like
works, so I'm happy.
Col.
>You wouldn't have any issues if you used a nested classpath which
>separates each classpath element
You wouldn't have any issues if you used a nested classpath which
separates each classpath element in a , instead of using a
property in a properties file.
But you can always replace "program files" by progra~1, i.e. the DOS
short name with no spaces. --DD
> -Original Message-
> From: Col
