ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Glozer <>
Subject RE: Zip task including dirs
Date Thu, 07 Sep 2000 14:13:16 GMT
Jesse, I would be appreciative if you were to do either.
Perhaps the flag would be the best solution?  I've created
my own jar task to include J2EE descriptors, and so I can
do it myself, but this seems like a good feature to include
in the general release.


-----Original Message-----
From: Jesse Glick []
Sent: Thursday, September 07, 2000 6:40 AM
Subject: Re: Zip task including dirs wrote:
> I like that behaviour and need it or else I end up creating
> files in directories that's sole purpose is to ensure that
> dir gets created. I have done this a lot with OS level zip
> utilities and it suxs :<.

I sent the patch that ensures directories are added fairly recently and
it was committed. It is more consistent with the behavior e.g. of the
JDK jar tool, which always creates the parent dirs, and at least Linux
zip. It seems safer to put them in even if it does make a few more
entries in the archive; some readers of the archive may blithely assume
that parent dirs exist (as happened to me).

Note: the current does not add directories that have no file in
them, even if they matched according to the fileset. I.e. it looks for
matching files only, then adds just their parents. This is arguably a
bug; I will try to send a patch to fix it if anyone is interested.

> An optional attribute that turned of this behaviour would be
> okay thou :P

This would be really easy if people wanted it--just add a new attribute
to, and if set, then in zipDir() return without doing anything.
Again I will send a patch if there is interest.


Jesse Glick   <>
NetBeans, Open APIs  <>
tel (+4202) 3300-9161 Sun Micro x49161 Praha CR

View raw message