ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bode...@locus.apache.org
Subject cvs commit: jakarta-ant WHATSNEW TODO
Date Tue, 25 Jul 2000 10:13:02 GMT
bodewig     00/07/25 03:13:01

  Modified:    .        TODO
  Added:       .        WHATSNEW
  Log:
  Removed items from the TODO list and added a WHATSNEW file.
  
  The latter should help us to follow the changes since 1.1 - I've
  already started to lose track. I ask the other commiters to update
  WHATSNEW as appropriate.
  
  Revision  Changes    Path
  1.2       +0 -25     jakarta-ant/TODO
  
  Index: TODO
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/TODO,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- TODO	2000/01/27 03:47:58	1.1
  +++ TODO	2000/07/25 10:13:01	1.2
  @@ -1,38 +1,13 @@
   TODO List:
   
  -  * write a target rule that reacts on class presence or more generally, a way
  -    to apply environment conditions that must be met in order for a target to 
  -    be executed. This is _vital_ for highly componentized systems where
  -    non-core parts of the software may be skipped if the required classes
  -    are not present in the build classpath.
  -
  -  * Improve error reporting on BuildException catches. Error should
  -    state which task and which target was active at the time the
  -    BuildException was popped.
  -
  -  * Improve error reporting on XML parse. Currently if the build.xml
  -    file is malformed we get some sort of odd SAX exception that could
  -    be better put.
  -
     * Provide an AbstractFileCompareTask class with prebuilt "srcfile"
       and "destfile" setter methods and whose execute method calls a
       "updateNeeded" method.
   
  -  * Transform task -- XSLT 
  -
  -  * Output logs in XML -- this would be a global option of the project
  -    (log location, verboseness, etc)
  -
  -  * Javac improvements -- support the "modern" 1.3 compiler
  -
     * Investigate some sort of command line "execute an instance of a
       task with these parameters" entry point. Maybe a
       `org.apache.ant.TaskMain task org.foo.BarTask attrib1=foo
       attrib2=bar` type entry point?
  -
  -  * Investigate some sort of "touch" functionality. Not sure how this
  -    could be done in a portable way -- maybe append 0 bytes to a file
  -    as a quick hack?
   
     * GUI front end -- examine tasks, add task properties, etc. Also,
       one button push build of a particular target.
  
  
  
  1.1                  jakarta-ant/WHATSNEW
  
  Index: WHATSNEW
  ===================================================================
  Changes from Ant 1.1 to the current sources
  
  Changes that could break older buildfiles:
  ------------------------------------------
  
  * copying of support files in <javac> has been removed.
  
  Other changes:
  --------------
  
  * New tasks (sql, junit, javacc) all pending documentation, some of
  them pending review.
  
  * <java> uses ClassLoader of its own in no-fork mode if a classpath is
  specified.
  
  * <style> will create the necessary target directories and reprocess
  all files if the stylesheet changes.
  
  * Path and EnumeratedAttribute moved to a new package
  org.apache.tools.ant.types.
  
  * New data types fileset and patternset - expected to get a broader
  use, pending documentation.
  
  * You can specify environment variables to the exec task - pending
  documentation.
  
  Fixed bugs:
  -----------
  
  * <chmod> didn't work when used as a directory based task.
  
  * Path didn't resolve relative filenames with respect to the Project's
  basedir.
  
  * Project didn't interpret the basedir attribute correctly in all
  cases.
  
  
  

Mime
View raw message