Return-Path: <jeremy.mawson@qsipayments.com>
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 79316 invoked from network); 24 Aug 2000 00:27:37 -0000
Received: from mail.qsi.com.au (HELO qsi.com.au) (203.52.108.133)
  by locus.apache.org with SMTP; 24 Aug 2000 00:27:37 -0000
Received: from keroppi ([192.168.21.60])
	by qsi.com.au (8.9.3/8.9.3) with SMTP id KAA23352
	for <ant-user@jakarta.apache.org>; Thu, 24 Aug 2000 10:24:10 +1000
Message-Id: <3.0.6.32.20000824102937.00a3dd80@192.168.21.17>
X-Sender: jeremym@192.168.21.17
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Thu, 24 Aug 2000 10:29:37
To: ant-user@jakarta.apache.org
From: Jeremy Mawson <jeremy.mawson@qsipayments.com>
Subject: CopyDir: Request for additional parameter
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Currently if you use copydir task in this fashion:

<copydir
    src="${SRC_DIR}"
    dest="${DEST_DIR}"
    includes="**/html/" />


All files in the HTML directories are copied with their relative paths.
Fair enough.

What I would really like to see is an additional option (a y/n param) to
ascertain whether the files under the html directories should be copied to
${DEST_DIR} precisely (ie not into subdirectories of ${DEST_DIR}).

Perhaps something like:

<copydir src="x" dest="y" relative="yes" /> would copy

  x
  |
  +--001
     |
     +--002
     |  |
     |  +--file002
     |
     +--file001

to 

  y
  |
  +--001
     |
     +--002
     |  |
     |  +--file002
     |
     +--file001


but <copydir src="x" dest="y" relative="no" /> would copy

  x
  |
  +--001
     |
     +--002
     |  |
     |  +--file002
     |
     +--file001

to 

  y
  |
  +--file001
  +--file002


What's the thinking out there?

Jem