> From: Diane Holt [mailto:[EMAIL PROTECTED]]


> As long as you're referencing the property in attributes that 
> deal with
> paths, you shouldn't need to worry about semicolon vs. colon 
> or backslash
> vs. foreslash. (And if you follow Dominique's suggestion to 
> build up the
> value based on a "basedir" [or other preceeding-directory] 
> property, then
> it won't look odd having colons -- eg.,
> ${basedir}/path1:${basedir}/path2.)

Won't that fail if basedir is set to something like "C:\xyz"?

When you refer to "paths" above, do you mean pathnames or
search paths? 


Daniel


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to