requested-features.txt

apache-ant-1.6.0-bin.zip 做jsp开发过程要用到的源码！

Status:
=======

The committers have cast votes on all items (except those that came in
too late) and the results are listed below - the next step will be a
design phase.

This list of items will be summarized into an Ant2 specification soon.

I. Things that don't affect the core but are requests for new tasks or
enhancements of existing tasks.
======================================================================

[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.

* Add a new datatype filterset to group token-filters 

  [ACCEPTED]

* make usage of particular filters/filtersets explicit in copy tasks

  [ACCEPTED]

* make facade tasks for things like javac (JikesImpl, ModernImpl etc)

  One candidate is jar with implementations for fastjar
  for example.

  [ACCEPTED]

* unify multiple similar tasks to use similar forms (ie all the javacc
  type tools)

  [ACCEPTED]

* Obfuscating task

  [ACCEPTED]

* Add an <ant> task that will find build files according to a fileset
  and invokes a common target in them.

  <anton>?

  [will need more discussion because of votes by Peter Donald and
                                                 Stefan Bodewig]

  [finally ACCEPTED]

* 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]

  [finally ACCEPTED]

* Include some more sophisticated loggers with the Ant distribution -
  especially for sending emails. Make the existing one more flexible
  (stylesheet used by XmlLogger).

  Could be part of the same module tasks would be developed in?

  [will need more discussion because of vote by Conor MacNeill]

  [finally ACCEPTED]

* make the default logger's output clear, informative, and terse.

  Actually, this is a little bit abstract, but doesn't apply to the
  core either.

  [will need more discussion because of vote by Conor MacNeill]

  [REJECTED - vetoes by Conot MacNeill and Stefan Bodewig]

* Better docs.

  More examples. Tutorials, beginner documents, reference sheets for
  tasks, printable version.

  [ACCEPTED]

* RPM task.

  [ACCEPTED]

* 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]

  [REJECTED - veto by Peter Donald]

* Task for splitting files (head/tail/split like functionality).

  [ACCEPTED]

* Task to create XMI from Java.

  [ACCEPTED]

* socksified networking tasks, SSH tasks.

  [Peter Donald expressed some legal concerns that might be overcome, 
                depending on the implementation]

* a reachable task that works much like available for network URLs.

  [ACCEPTED]

* 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]

  [REJECTED - vetoes by Conor MacNeill, Glenn McAllister and Stefan Bodewig]

* Task to extract classes from a JAR file that a given class depends
  on.

  Based on <depend> or IBM's JAX for example.

  [ACCEPTED]

* 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]

* jsp-compilation task

  Sounds like a candidate for a facade task.

  [ACCEPTED]

* URL-spider task that checks links for missing content or server errors

  [ACCEPTED]

II. Abstract goals that need to be abstract until we get into design
decisions.
======================================================================

During discussion it became obvious, that some things from this list
are goals for Ant and some should be guidelines for developers,
therefore there are two flavors, [ACCEPTED] and [ACCEPTED AS GUIDELINE].

* Provide a clear mission statement for Ant.

  [ACCEPTED]

* Main goals: Simplicity, Understandability, Extensibility

  [ACCEPTED]

* remove magic properties if at all humanly possible

  [ACCEPTED]

* remove as much dependency on native scripts as possible.

  [ACCEPTED]

* clean object model (ie Project/Target/Task)

  [ACCEPTED]

* good event model to integrate well with IDE/GUI/whatever

  [ACCEPTED]

* use a consistent naming scheme for attributes across all tasks

  [ACCEPTED]

* keep build file syntax as compatible to Ant1 as possible -
  i.e. don't break something just because we can.

  [ACCEPTED]

* keep the interface for Tasks as similar to the one of Ant1 as
  possible - i.e. don't break something just because we can.

  [ACCEPTED]

* Ant should be cancelable

  [ACCEPTED]

* no commit of new features without documentation

  [ACCEPTED AS GUIDELINE]

* no commit of new features without testcases

  [ACCEPTED AS GUIDELINE]

III. Things that are simple, easy to implement, where we expect the
committers to agree
======================================================================

* namespace support so different concerns can occupy different namespaces
  from ant (thus SAX2/JAXP1.1)

  [ACCEPTED]

* Java2

  [ACCEPTED]

* remove all deprecated methods, attributes, tasks

  [ACCEPTED]

* allow all datatypes to be defined anywhere - i.e. as children of
  project as well as of target.

  [ACCEPTED]

* make properties fully dynamic, i.e. allow their value to be reassigned

  [will need more discussion because of vote by Glenn McAllister and
                                                Conor MacNeill]

  [finally ACCEPTED]

* unify the namespace of all data types (ie properties + filesets +
  patternset + filtersets).

  [ACCEPTED]

* add a user defined message if a target will be skipped because the
  if/unless attribute says so.

  [ACCEPTED]

* allow user-datatypes to be defined via a <typedef> similar to <taskdef>.

  [ACCEPTED]

IV. Things we probably agree upon but need to discuss the details or
decide between several possible options.
======================================================================

[ACCEPTED] means, the goal/idea is fine, not that a decission on a
particular implementation has been made.

* The ability for GUI/IDE tools to integrate easily with object model
  without reinventing the wheel and writing their own parser (which
  antidote was forced to do). 

  Two suggested solutions were allowing GUI developers to extend
  object model (ie GUITask extends Task) or to have Task as interface
  (ie GUITask implements Task). This way the GUI tasks could be W3C
  DOM Elements, have property vetoers/listeners etc.

  [ACCEPTED]

* support for numerous frontends - from command line over GUI to servlets

  corollary of the above?

  [ACCEPTED]

* Fully interpreted at runtime. This almost requires some form of
  abstraction/proxy that stands in place of tasks till it is
  interpreted.  This can be hashtables/simple dom-like model/whatever

  [ACCEPTED]

* provide utility classes to aid in building tasks. ie like up-to-date
  functionality abstracted

  Need to become more specific here.

  [ACCEPTED]

* make ant-call a low cost operations so it can certain
  optional/template-like operations

  corollary of "fully interpreted at runtime"?

  [ACCEPTED]

* allow facilities to build projects from multiple sources. ie CSS+xml
  or XSLT+ XML or Velocity+text or database or from inside jars or normal 
  build.xmls etc.

  allow the project tree to be built dynamically.

  [ACCEPTED]

* move to a system that allows docs to be generated - doc snippets
  should be included with the tasks they document.

  Which DTD? Which tools for generation?

  [ACCEPTED]

* allow tasks to be loaded from jars. tasks should be indicated by
  either xml file in TSK-INF/taskdefs.xml or manifest file.

  [ACCEPTED]

* allow documentation to be stored in .tsk jars

  corollary of the two points above?

  [ACCEPTED]

* better scripting/notification support so the hooks are available to
  send notifications at certain times.

  Which hooks and where?

  [will need more discussion because of vote by Peter Donald and
                                                Simeon Fitch]

  [REJECTED - vetoes by Conor MacNeill, Peter Donald and Simeon Fitch]

* separate tasks into .tsk jars somehow. (Probably via function - ie
  java tasks, file tasks, ejb tasks).

  Decide on categories.

  [will need more discussion because of vote by Conor MacNeill]

  [finally ACCEPTED]

* make separate build files easy (ala AntFarm) and importing different
  projects a breeze

  [ACCEPTED]

* provide support for user defined task configurations - i.e. give
  users the ability to specify a default value for attributes (always
  use debug="true" in <javac> unless something else has been
  specified). 

  Three ideas so far: a CSS like language, a <taskconfig> element,
  properties following a specific naming scheme.

  [ACCEPTED]

* support more control over the properties that are going to be passed
  to subprojects (modules)

  [ACCEPTED]

* Ask for a new CVS module for Ant tasks.

  We need to define rules for this to work - maybe the rules proposed
  for the commons project could give us a start.

  [will need more discussion because of vote by Conor MacNeill]

  [REJECTED - vetoes by Conor MacNeill and Glenn McAllister]

* It should be possible to modify details of the actual build (e.g. classpath,
  used compiler) without the need to change the build specification.

  Do build.compiler and build.sysclasspath cover everything or do we
  need to add more stuff like this?

  [will need more discussion because of vote by Conor MacNeill]

  [REJECTED - veto by Conor MacNeill]

* Task to prompt for user input.

  Does affect core as we need a means to request input from the Frontend.

  [ACCEPTED]

* Add cvs login feature.

  Requires handling of user input.

  [ACCEPTED]

* Easier installation process. GUI - maybe webstart from the homepage.