> 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.
Only if you want to name your volumes jar or classpath or
something like that in netware. Hey, it is an exception, right?
> Hummm, and all that just because you want to overload the
> meaning of the file attribute. Really, does this makes any sense?
That isn't the intent. I am not proposing this just to have the fun of
overloading the file attribute, if that's how it is coming across. I just
want to understand why a separate url attribute is better. Your example
which demostrated an exception did help.
> You are just making more dificult to use files.
I will do my best to avoid doing that ;-)
> 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.
A separate srcUrl attribute, it will be then - assuming we even want to
introduce
url based copy functionality to the <copy> task.
Magesh
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
