Consider allowing the user to configure the ant system by setting the + following path types.
++ The default search path will probably include a per-user path element, + a workspace path element and a system path elemtn that are searched in + that order. Some possible defaults; +
+There are 2 parts to this broad topic: Allow Ant 1.x build scripts to be
@@ -64,67 +92,97 @@
The file data-types, such as The file data-types, such as
+ <fileset>
and
- <path>
, are some of the most widely used parts of Ant 1.x.
- Unfortunately, they aren't particularly extensible.<fileset>
and
+
+ <path>
, are some of the most widely used parts of Ant 1.x.
+ Unfortunately, they aren't particularly extensible.
+
FileObject
, rather than java.io.File
.
- This process has started, in the antlib.vfile
package.
+
+ FileObject
, rather than
+ java.io.File
.
+ This process has started, in the
+ antlib.vfile
package.
+
-
AbstractNameFileSelector
to use Ant 1 style patterns
- matches, rather than Globs patterns.DefaultFileSet
. Also add a
- file selector implementation that matches everything except the default
- excludes.
+
+
AbstractNameFileSelector
to use Ant 1 style patterns
+ matches, rather than Globs patterns.
+ DefaultFileSet
. Also add a
+ file selector implementation that matches everything except the default
+ excludes.
+
-
+
+
-
+
+
-
+
+
-
ClassLoaderManager
to evaluate to the classpath of any
- 'library' (e.g. system classpath, ant runtime, tools.jar,
- an antlib, an installed extension, or the system classes of another JVM
- for cross-compiling).
+
+
ClassLoaderManager
to evaluate to the classpath of any
+ 'library' (e.g. system classpath, ant runtime, tools.jar,
+ an antlib, an installed extension, or the system classes of another JVM
+ for cross-compiling).
+
-
<move>
, <delete>
,
- <touch>
and <mkdir>
tasks on top
+
+
+
+ <move>
,
+ <delete>
,
+
+ <touch>
and
+ <mkdir>
tasks on top
of the VFS and the new file data-types. Might be some scope for generalising
- 'touch' and 'mkdir' into a single task.
lib
and ext
directories.lib
and
+ ext
directories.
+ ant-services.xml
descriptor.ant-services.xml
descriptor.
+ <http>
and <socket>
- conditions to an antlib. Need to resolve how these will be passed a logger.<uptodate>
task a condition, and move to
- an antlib.<is-set>
condition into is-set and is-true conditions.<if>
task to take any condition implementation.<if>
task.<available>
condition into separate conditions
- that test for the availability of a class, or a resource.crimson.jar
to bin/lib
in the distribution,
- and make to other jars via the extension mechanism.<http>
and
+ <socket>
+ conditions to an antlib. Need to resolve how these will be passed a logger.
+ <uptodate>
task a condition, and move to
+ an antlib.
+ <is-set>
condition into is-set and is-true conditions.
+ <if>
task to take any condition implementation.
+ <if>
task.
+ <available>
condition into separate conditions
+ that test for the availability of a class, or a resource.
+ crimson.jar
to
+ bin/lib
in the distribution,
+ and make to other jars via the extension mechanism.
+