I've not counted Sim's "-1 (not in core)" votes as "we'll need some
extra discussion" but think they are covered by the following
disclaimer:
[ACCEPTED] for a task doesn't mean that task will be core tasks (or
even be supplied by a voter), just that having them (as optional
tasks) would be acceptable.
Let me know if this is not OK with you.
The [ACCEPTED] stuff:
============================================================================
* Add a new datatype filterset to group token-filters
* make usage of particular filters/filtersets explicit in copy tasks
* make facade tasks for things like javac (JikesImpl, ModernImpl etc)
* unify multiple similar tasks to use similar forms (ie all the javacc
type tools)
* Obfuscating task
* Better docs.
* RPM task.
* Task for splitting files (head/tail/split like functionality).
* Task to create XMI from Java.
* a reachable task that works much like available for network URLs.
* Task to extract classes from a JAR file that a given class depends
on.
* jsp-compilation task
* URL-spider task that checks links for missing content or server errors
Borderline case
===========================================================================
* socksified networking tasks, SSH tasks.
[Peter Donald expressed some legal concerns that might be overcome,
depending on the implementation]
Needs extra discussion and a final vote
===========================================================================
* Unify <available> and <uptodate> into a more general <condition>
task, support AND/OR of several tests here.
[will need more discussion because of vote by Peter Donald]
* Add an <ant> task that will find build files according to a fileset
and invokes a common target in them.
[will need more discussion because of votes by Peter Donald, Simeon Fitch
and Stefan Bodewig]
* Add a JavaApply task that executes a given class with files from a
fileset as arguments - similar to <apply>.
[will need more discussion because of votes by Peter Donald and
Stefan Bodewig]
* Include some more sophisticated loggers with the Ant distribution -
especially for sending emails. Make the existing one more flexible
(stylesheet used by XmlLogger).
[will need more discussion because of vote by Conor MacNeill]
* make the default logger's output clear, informative, and terse.
[will need more discussion because of vote by Conor MacNeill]
* add an attribute to <property> to read in an entire file as the
value of a property.
[will need more discussion because of vote by Peter Donald]
* make PATH handling consistent. Every task that has a PATH attribute
must also accept references to PATHs.
[will need more discussion because of vote by Stefan Bodewig]
