Return-Path: 
 <notifications-return-15421-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: (qmail 14645 invoked from network); 17 Feb 2011 15:47:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 17 Feb 2011 15:47:57 -0000
Received: (qmail 44828 invoked by uid 500); 17 Feb 2011 15:47:57 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 44750 invoked by uid 500); 17 Feb 2011 15:47:55 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 44737 invoked by uid 99); 17 Feb 2011 15:47:54 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 15:47:54 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 15:47:52 +0000
Received: from thor.apache.org (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p1HFlUv3016926
	for <notifications@ant.apache.org>; Thu, 17 Feb 2011 15:47:30 GMT
Received: (from daemon@localhost)
	by thor.apache.org (8.13.8+Sun/8.13.8/Submit) id p1HFlUCJ016925;
	Thu, 17 Feb 2011 10:47:30 -0500 (EST)
Date: Thu, 17 Feb 2011 10:47:30 -0500 (EST)
Message-Id: <201102171547.p1HFlUCJ016925@thor.apache.org>
From: bugzilla@apache.org
To: notifications@ant.apache.org
Subject: DO NOT REPLY [Bug 49492] The fileset resource collection doesn't
 handle file/directory names with spaces
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ant
X-Bugzilla-Component: Core
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mbenson@apache.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: notifications@ant.apache.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
In-Reply-To: <bug-49492-48744@https.issues.apache.org/bugzilla/>
References: <bug-49492-48744@https.issues.apache.org/bugzilla/>
X-Bugzilla-URL: https://issues.apache.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-Virus-Checked: Checked by ClamAV on apache.org

https://issues.apache.org/bugzilla/show_bug.cgi?id=49492

--- Comment #8 from Matt Benson <mbenson@apache.org> 2011-02-17 10:47:25 EST ---
(In reply to comment #5)
> I am having a similar issue with <FILELIST> breaking apart filenames with
> spaces in the "files" string.  In addition to breaking apart the string, I am
> relying on <FILELIST> to resolve relative pathnames, so I'm not sure that the
> <RESOURCELIST> workaround will work for me.

Firstly, you can use any resource inside resourcelist.  Now, I assume that what
you are trying to pass to filelist@files is a property, else you'd just be
using nested <file> elements, right?  So you have a <propertyresource>.  I
assume you must be using commas for your token, so you could use a <tokens>
resourcecollection to break up your propertyresource.  To add leading paths,
you could add another level of indirection into the <tokens>:  a <concat>
task/resourcecollection using a filterchain configured with a prefixlines
filter.  Actually once you're using <concat> you can probably skip the <tokens>
collection altogether and use it to tokenize your comma-delimited stuff *and*
prefix the resulting lines, passing the <concat> resource directly to
<resourcelist>.  I am thus 99% confident that a solution *can* be made to work
using <resourcelist>.  I don't have any major antipathy towards making
separators configurable in <filelist>; however it would introduce an
inconsistency between filelist and fileset/files/dirset that is IMO
unnecessary.  These other types are somewhat different than filelist due to the
fact that they all deal with directory scanning and therefore support
includesfile/excludesfile as a means of specifying patterns with embedded
spaces.  Of course, knowing that <filelist> supports the nested <file> element
for this purpose (as documented in the manual), an alternative could be to use
antcontrib:for to iterate over your comma-delimited property, then use the
<augment> task to add the nested <file> elements one at a time.

Please follow up on user@ant.apache.org if you need more information about any
of the approaches I've outlined here.

Matt

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.