ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Magesh Umasankar" <>
Subject Re: [PATCH] Copy task recognizes URLs as file attributes
Date Wed, 28 Nov 2001 00:06:24 GMT
> So, now I need to have two buildfiles, one for NetWare with
> 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
> use a OS dependant feature). <copy file="${myfile}" .../> has to be OS
> no matter what OS or computation environment is being used.

A separate srcUrl attribute, it will be then - assuming we even want to
url based copy functionality to the <copy> task.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message