From dev-return-77953-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Wed Jan 24 19:26:32 2007 Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 49342 invoked from network); 24 Jan 2007 19:26:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Jan 2007 19:26:30 -0000 Received: (qmail 27426 invoked by uid 500); 24 Jan 2007 19:26:34 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 27368 invoked by uid 500); 24 Jan 2007 19:26:34 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 27347 invoked by uid 99); 24 Jan 2007 19:26:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jan 2007 11:26:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [88.84.142.181] (HELO v30161.1blu.de) (88.84.142.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jan 2007 11:26:26 -0800 Received: (qmail 27869 invoked by uid 2525); 24 Jan 2007 20:18:09 +0100 To: dev@ant.apache.org Subject: Re: tar task problems X-Draft-From: ("nnfolder:mail.jakarta-ant" 79327) References: <21B42DA9-90DE-49D1-A291-F36766606747@apache.org> From: Stefan Bodewig Date: Wed, 24 Jan 2007 20:18:09 +0100 In-Reply-To: <21B42DA9-90DE-49D1-A291-F36766606747@apache.org> (Torsten Curdt's message of "Wed, 24 Jan 2007 18:46:28 +0100") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org On Wed, 24 Jan 2007, Torsten Curdt wrote: > AFAIU the only way of modifying TGZs and retain meta date like > permissions and ownerships is to nest the TAR with the UNTAR (ZIP/ > UNZIP) process (as TarResource object getting passed through). You are correct. does have an update attribute, but tar doesn't. > While this seems to work fine for ZIP, the TAR task bails out with > > "Problem creating TAR: request to write '0' bytes exceeds size in > header of '-1' bytes for entry ''" Ouch. It might be due to your specific tar archive, I think we do have a unit test that re-tars a tar, but I could be wrong. I'm not aware of any prior report of this bug, but then again a lot of issues have been opened without me following close enough. If you can provide a simple test tar.gz for us, writing an AntUnit test would be trivial. > Also I am wondering why mappers are not supported. > > > > > > > > > > By design or would a contribution be welcome? :) Not by design, just because nobody added it. If you wanted to contribute anything, a MappedResourceCollection like might be worth a try as it would add mapping functionality to any task accepting resource collections. This approach wouldn't work in your case, though, since we'd lose permission information (the task wouldn't know there is a tarfileset decorated by the mapped collection). Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org