ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bode...@apache.org
Subject cvs commit: ant WHATSNEW
Date Wed, 19 Feb 2003 07:34:31 GMT
bodewig     2003/02/18 23:34:31

  Modified:    .        WHATSNEW
  Log:
  housekeeping
  
  Revision  Changes    Path
  1.357     +32 -23    ant/WHATSNEW
  
  Index: WHATSNEW
  ===================================================================
  RCS file: /home/cvs/ant/WHATSNEW,v
  retrieving revision 1.356
  retrieving revision 1.357
  diff -u -r1.356 -r1.357
  --- WHATSNEW	9 Feb 2003 12:17:16 -0000	1.356
  +++ WHATSNEW	19 Feb 2003 07:34:30 -0000	1.357
  @@ -52,12 +52,13 @@
   
   * <junit> will now produce output when a test times out as well.
   
  -* The starteam stcheckout, stcheckin tasks now correctly compute status of files
  -  against whatever local tree they are run against and, optionally, will not
  -  process a file if it is current.  Previously you had to process everything
  -  unless you ran against the default folder which wasn't the normal use-case for
  -  ant-starteam.  The stlist task now similarly displays that status correctly
  -  making it a more generally useful tool.
  +* The starteam stcheckout, stcheckin tasks now correctly compute
  +  status of files against whatever local tree they are run against
  +  and, optionally, will not process a file if it is current.
  +  Previously you had to process everything unless you ran against the
  +  default folder which wasn't the normal use-case for ant-starteam.
  +  The stlist task now similarly displays that status correctly making
  +  it a more generally useful tool.
   
   * <replace> would count some internal character replacements when
     reporting the number of replaced tokens.
  @@ -116,14 +117,23 @@
     Package information and addition of classes specified in the Class-Path
     element of a Jar's manifest.
   
  -* It is now possible in <exec> to resolve the executable to a project basedir or
  -  execution dir relative executable. The resolveExecutable must be used to 
  -  pick up such executables.
  +* It is now possible in <exec> to resolve the executable to a project
  +  basedir or execution dir relative executable. The resolveExecutable
  +  must be used to pick up such executables.
   
  -* splash screen wouldn't disppear when build was finished.
  +* splash screen wouldn't disappear when build was finished.
   
  -* <exec> output and error streams can now be redirected independently to either
  -  a property or a file (or both)
  +* <exec> output and error streams can now be redirected independently
  +  to either a property or a file (or both)
  +
  +* <tar>'s up-to-date check didn't work for nested <(tar)fileset>s.
  +
  +* <exec> now supports OS/2.
  +
  +* <zip> and friends would only update/recreate existing archives if
  +  the files to add/update have been newer than the archive.
  +
  +* <javadoc>'s <link> element could fail for offline="true" on some JDKs.
   
   Other changes:
   --------------
  @@ -132,7 +142,8 @@
   * The start and end tokens for <translate> may now be longer than a
     single character.
   
  -* <setproxy> lets you set the username and password for proxies that want authentication
  +* <setproxy> lets you set the username and password for proxies that
  +  want authentication
   
   * <loadproperties> has a new encoding attribute.
   
  @@ -201,8 +212,6 @@
     works for the code generated by the Sun java compiler. It may not work for
     all compilers.
   
  -* <tar>'s up-to-date check didn't work for nested <(tar)fileset>s.
  -
   * a new attribute "globalopts" can be added to all Perforce tasks.
     You can put in it all the strings described by p4 help usage. Refer to 
     the docs for more information.
  @@ -211,15 +220,15 @@
     replacing in files that are in a different encoding than the
     platform's default.
     
  -* The <exec> task may now have its input redirected from either a file or
  -  a string from the build file. The error output can be separated to a different
  -  file when outut is redirected. standard error may be logged to the Ant log
  -  when redirecting output to a file
  +* The <exec> task may now have its input redirected from either a file
  +  or a string from the build file. The error output can be separated
  +  to a different file when outut is redirected. standard error may be
  +  logged to the Ant log when redirecting output to a file
     
  -* The <java> task also supports the input redirection and separate error streams
  -  introduced to the <exec> task. In addition, it is now possible to save the 
  -  output into a property for use within the build file as was possible with <exec>
  -  in Ant 1.5
  +* The <java> task also supports the input redirection and separate
  +  error streams introduced to the <exec> task. In addition, it is now
  +  possible to save the output into a property for use within the build
  +  file as was possible with <exec> in Ant 1.5
   
   Changes from Ant 1.5.1Beta1 to 1.5.1
   ====================================
  
  
  

Mime
View raw message