Return-Path: <Arnout.Kuiper@nl.origin-it.com>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 3370 invoked from network); 20 Apr 2000 17:09:12 -0000
Received: from gw-nl1.origin-it.com (@193.79.128.34)
  by locus.apache.org with SMTP; 20 Apr 2000 17:09:12 -0000
Received: from mail.nl.origin-it.com (localhost.origin-it.com [127.0.0.1])
          by gw-nl1.origin-it.com with ESMTP id TAA25706
          for <ant-dev@jakarta.apache.org>;
 Thu, 20 Apr 2000 19:09:10 +0200 (MEST)
          (envelope-from Arnout.Kuiper@nl.origin-it.com)
Received: from mail.nl.origin-it.com(172.16.127.67) by gw-nl1.origin-it.com
 via mwrap (4.0a)
	id xma025704; Thu, 20 Apr 00 19:09:10 +0200
Received: from nlehx900.ehvovh.nl.origin-it.com
 (nlehx900.ehvovh.nl.origin-it.com [172.16.92.111])
	by mail.nl.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id TAA03340
	for <ant-dev@jakarta.apache.org>; Thu, 20 Apr 2000 19:09:10 +0200 (MET DST)
Received: by nlehx900.ehvovh.nl.origin-it.com with Internet Mail Service
 (5.5.2448.0)
	id <JHJA641X>; Thu, 20 Apr 2000 19:09:10 +0200
Message-ID: 
 <E1B81A5627BAD01191B500805FC16B0E77AB54@nlnwx001.nwgbak.nl.origin-it.com>
From: "Kuiper, Arnout" <Arnout.Kuiper@nl.origin-it.com>
To: "'ant-dev@jakarta.apache.org'" <ant-dev@jakarta.apache.org>
Subject: RE: Path & dir separators (was Re: Ant Principles)
Date: Thu, 20 Apr 2000 19:09:09 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

> From: Thomas Haas [mailto:thomas.haas@softwired-inc.com]
[Snip]

> Proposal:
> 
>    * Define pathes using nested elements (unless passed in as 
> property).
>      Elements are files (or directories) defined by the rules 
> for files

Does this mean that paths cannot be passed as task attributes anymore?

[Snip]

What is the scope of your proposal? Does it only cover paths (sets of
directories/files) or does it also cover single files and single
directories? If it also covers the latter case, won't the task syntax
of some simple tasks become too lengthy?
Copying a directory will then become something like:

  <copydir>
    <srcdir>
      <element file="../foo/"/>
    </srcdir>
    <destdir>
      <element file="../bar/"/>
    </destdir>
  </copydir>

instead of

  <copydir srcdir="../foo/" destdir="../bar/"/>

We can combine these two if the srcdir attribute is of type "Path", and
the Path class has a constructor accepting a String, which represents
some path-format (either the format of the local platform, the to bew
defined
X-platform Ant format or the "popular Ant" format). See some other postings
on reflection and nested elements.

Don't misunderstand me here, I like your path concept, but I'm trying
to find a balance between the number of characters I have to type, and
the flexibility;-)

Cheers,

  Arnout