Thanks so much! Yes, a CopyFiles task would make sense, it would separate two functionalities currently mashed together.
As for the compressed/uncompressed, well, yes, I would like such a patch, although if it's going to be in the product pretty soon, I could wait. I'm going through some tests and evaluation, and want to move our organization away from a nightmare of Imakefiles all the processing necessary to create makefiles from Imakefiles and then all the overhead of building with them... But, we still have several products that are JDK 1.1.7 and JDK 1.1.8 based, so we need that uncompressed jar capability if we are going to be adopt 'Ant'. Is there a particular list I should subscribe to for announcements about releases and features, or does that happen here? Thanks again! -ken Stefan Bodewig wrote: > > >>>>> "KW" == Ken Wood <[EMAIL PROTECTED]> writes: > > KW> 1. The jar task doesn't have the '0' option that 'jar' has, i.e. > > You are right. Both zip and jar will create compressed files. > > I propose to add a boolean "compress" attribute to the zip task (jar > would inherit it from zip) that defaults to true and set the > OutputStream to ZipOutputStream.DEFLATED or ZipOutputStream.STORED > according to this option. > > This is quite straight forward and I could supply a patch for it. > > KW> 2. While it's not an issue, I wonder if there is a simple way to > KW> suppress the "copying of support files" that the javac task does. >
