ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jose Alberto Fernandez <>
Subject RE: Core Task spec 0.1
Date Thu, 29 Jun 2000 18:28:09 GMT
It would be nice if you also integrate PATH specifications that work the
same way as the path sets. So the idea would be to define a pathset and then
be able to reuse it in the different tasks that require paths or classpaths.

<pathset name="compile.classpath" >
  <include name="x/y"/>
  <include name="lib/*.jar"/>
  <exclude name="lib/rt.jar"/>
  <javac ...>
   <classpath name="compile.classpath"/>

Or something like that.

-----Original Message-----
From: Stefan Bodewig []
Sent: Thursday, June 29, 2000 12:56 AM
Subject: Re: Core Task spec 0.1

>>>>> "AK" == Arnout J Kuiper <> writes:

 AK> Comments please...

I too like the idea of the fileset container, this might obsolete my
proposal to rework MatchingTask so I will hold back any modifications
I had planned.

fileset should get a defaultexcludes attribute.

I agree with Glenn that copy, move and delete should take filesets as
the source of the operation - drop srcdir and the include/exclude
elements in favor of a nested fileset element - or even multiple
fileset elements.

Unjar would be just another name for Unzip or do you expect it to add

Gzip, Gunzip, Unjar, Untar and Unzip could benefit from an overwrite
attribute while an attribute to Jar, Tar and Zip to specify whether to
update or replace an existing archive might be useful.

Add Mkdir and maybe Chmod and the upcoming Touch to the basic
file system operations.

Another group of operations is "basic file manipulation operations" with
FixCRLF, Keysubst, Replace and the filtering behavior of file copying
tasks (are you proposing to drop the last one?). ISTR Thomas Haas had
a Task that unified some of these operations.

Add Exec and Java (and Ant?) as basic execution tasks.


View raw message