Return-Path: 
 <ant-dev-return-20384-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 69088 invoked from network); 27 Nov 2001 23:18:37 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 27 Nov 2001 23:18:37 -0000
Received: (qmail 29381 invoked by uid 97); 27 Nov 2001 23:18:40 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 29362 invoked by uid 97); 27 Nov 2001 23:18:39 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 29348 invoked from network); 27 Nov 2001 23:18:38 -0000
Message-ID: <000d01c1779b$3bdc15c0$9240d6d1@compaq>
Reply-To: "Magesh Umasankar" <umagesh@apache.org>
From: "Magesh Umasankar" <umagesh@apache.org>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
References: <20011127213141.1653.qmail@mailweb29.rediffmail.com>
 <007d01c17794$7920c360$0201a8c0@nordwand>
Subject: Re: [PATCH] Copy task recognizes URLs as file attributes
Date: Tue, 27 Nov 2001 18:28:33 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> >My point is why should the protocol matter?  Why *shouldn't* the
attribute
> "file" be overloaded?
>
> 1. it aint a file, it is a URL. I know that you can argue that it is a
> remote file, but that assumes that the url endpoint is 'legacy' static
> content, not some dynamically created or retrieved thing.

One is a local stream, other is a Remote stream - no major difference.
In fact this idea has been discussed in other forms - Peter had
suggested in the future we adopt as a valid command

ant -buildfile jar:file:somefile.jar!/install.xml

in http://marc.theaimsgroup.com/?l=ant-dev&m=100681347618956&w=2

So what would we do there?

> 2. The more information we provide in the XML syntax, the less
> interpretation which needs to be included in the runtime, which gives more

Yep.  I agree from developer's perspective - lot less headache.

> list and wherever an attribute was overloaded:
>  <target depends="task1,task2" >
>  <exec os="windows 2000, unix" > (actually this is worse, as we just
> substring match, so "windows" would still get a hit>
>  includes="...", excludes="..."

So it caught your friend's eyes too? ;-)

> 3. Remember that email about how we should have consistent property names,
> srcFile and srcDir, destFile and destDir. Using srcURL and destURL would
be
> consistent. Yes, I know that <copy> isnt consistent with this scheme, but
> that is a historical feature. We could make it consistent...

I sincerely have no complaints what to name the url attribute - only issue
is whether one such needs to exist and since I have heard at least
3 voices for it, I guess I will just give in ;-)

Magesh




--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>