ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject AW: [Fwd: Some Thoughts on Ant 1.3 and 2.0]
Date Tue, 24 May 2005 06:28:52 GMT
> (*) Extension tasks
> Make extending Ant as simple as possible, i.e. drop a jar file in a
> specific directory (ANT_HOME/ext globally or ~/.ant/ext on a user by
> user basis).
> This jar file must include <taskdef>s to define the tasks, Schema
> files to describe the tasks and documentation in the XML format we
> agreed on.
> The Schema file is there to support GUI tools for example. They could
> prompt for required attributes, let you select enumerated attributes
> from a list, require integer attributes to really contain numbers ...

First is done with AntLibs and autoloading via xml-namespaces.
But I like the 3rd paragraph - but could be be done via java source?
- annotations and XDoclet/apt generates such a file
- something like

  public interface ConfigurationCheck {
      /** Returns all names of required attributes. */
      public static String[] getRequiredAttributes();

      /** Returns all names of required nested elements. */
      public static String[] getRequiredElements();

      /** This instance is valid, means all required values are set
correctly. */
      public boolean validate();

How the IDEs solve that at the moment?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message