Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 1769 invoked from network); 7 Oct 2003 18:35:55 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Oct 2003 18:35:55 -0000 Received: (qmail 8879 invoked by uid 500); 7 Oct 2003 18:35:42 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 8841 invoked by uid 500); 7 Oct 2003 18:35:42 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 8828 invoked from network); 7 Oct 2003 18:35:42 -0000 Received: from unknown (HELO palrel11.hp.com) (156.153.255.246) by daedalus.apache.org with SMTP; 7 Oct 2003 18:35:42 -0000 Received: from gort.cv.hp.com (smtp1.cv.hp.com [15.0.200.101]) by palrel11.hp.com (Postfix) with ESMTP id CD5ED1C004F6 for ; Tue, 7 Oct 2003 11:35:46 -0700 (PDT) Received: from iseran.com (chamonix.cv.hp.com [15.87.26.62]) by gort.cv.hp.com (Postfix) with ESMTP id 7720A1FD70 for ; Tue, 7 Oct 2003 11:52:05 -0700 (PDT) Message-ID: <3F830782.8030501@iseran.com> Date: Tue, 07 Oct 2003 11:35:46 -0700 From: Steve Loughran User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ant Developers List Subject: Re: files and properties References: <20031007143637.78474.qmail@web20405.mail.yahoo.com> In-Reply-To: <20031007143637.78474.qmail@web20405.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Matt Benson wrote: > (Apologies in advance for the length of this post) > > The feeling has been growing in me that a future > version of Ant should abstract the concept of file I/O > with an interface that can supply InputStreams and > OutputStreams, or Readers and Writers if we can > restrict to character content--which would be quite > possible--or both. With this type of abstraction a > property could be treated as a file (existing > properties could be read-only and throw appropriate > Exceptions when overwrite attempts were made. This > could add, I feel, a good deal of flexibility for a > fairly low cost. > > I guess the motivating factor to this idea is my > intense dislike of the clutter of temp files, > especially when they do very little. > > Comments? There has been discussion on a better abstract file/directory abstraction, as there are so many more things than a file system that can be a source or a dest. Properties are an interesting one, the inside of JAR and ZIP files another, remote ftp, http and SCP connections a third. There is the VFS project in the jakarta commons sandbox http://jakarta.apache.org/commons/sandbox/vfs/index.html that implements this. The ant tasks there look kind of slick. I should play with them myself. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org