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 Tue, 27 Nov 2001 20:07:00 GMT

----- Original Message -----
From: "Peter Donald" <>
To: "Ant Developers List" <>
Sent: Tuesday, November 27, 2001 2:51 PM
Subject: Re: [PATCH] Copy task recognizes URLs as file attributes

> I would prefer you not use an attribute name of "file" but instead use

I too thought of that instead of overloading file itself.  But if you look
at it like
the URL results in a file which is to be copied, then wouldn't using file
make sense?  I was hoping to narrow the difference between a network file
and a disk file - say in the future, we have something like

ant -buildfile

We wouldn't introduce the concept of buildurl, would we? Also, in Java, it
boils down to InputStreams and OutputStreams...  So, why differentiate?
I am just looking for reasons.  One other point I considered was URL also
wraps around file using file:// protocol...

> or similar. I would also prefer not to have password/username attributes
> because I think it is overloading the copy task too much... Most URL
> allow you to embed usernam,e/password combo into url - would this work ?

Yes, that would work, but I was trying to be consistent with the Get task.
I look at Get as a sibling of Copy except that it works on a network file...
Please let me know if username/password needs to stay, given this context,
to be chucked out?



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

View raw message