From: "Magesh Umasankar" <[EMAIL PROTECTED]>
> > In NetWare one can have a disk mounted under the name "jar"
> > which you see can cause all kinds of problems on interpreting the meaning
> > of the argument.
>
> Alright. I see your point. The exceptional case that you note
> can still be solved by adding an attribute treatAsURL which by default
> is true and user may want to turn it off ;-)
>
So, now I need to have two buildfiles, one for NetWare with treatAsURL=false
on every <copy> and one for other OSs with treatAsURL=true.
Hummm, and all that just because you want to overload the meaning of the file
attribute.
Really, does this makes any sense? You are just making more dificult to use
files.
My point is that buildfiles are suppose to be OS independent (unless you
actually
use a OS dependant feature). <copy file="${myfile}" .../> has to be OS
independant
no matter what OS or computation environment is being used.
Jose Alberto
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
