ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Seessle" <>
Subject Re: Redirecting output and background processes
Date Wed, 27 Sep 2000 09:02:46 GMT
Some time ago there was a task named propertyFile which was submitted but never commited to
CVS. This task was able to write property-files and to (optionally) modify properties while
writing it (i.e. increment a build-number).

This task had the same problem teh echo task would have - it will do open/write/close sequence
foe every single line, and it would possibly even need an additional attribute append="true/false"
to make everyone happy.

I've modified the propertyFile-task because I had problems with it on WinNT (sometimes failed
to delete the file for unknown reasons, but worked immediately if only one write is done for
the file). 

It will currently accept (for example) the following syntax:

    <propertyfile file="${build.inf}" 
                  message="${COPYRIGHT.MESSAGE}\\\\Do not edit manually!">
       <entry key="product.version.major" type="int"  value="5"/>
       <entry key="product.version.minor" type="int"  value="0"/>
       <entry key=""   type="int"  value="0" />
       <entry key=""   type="int"  operation="+" />
       <entry key=""    type="date" operation="now" />

Should I maybe resubmit this (after cleaning up the source)? Would be as an optional task
this time :-)

  ----- Original Message ----- 
  From: Jose Alberto Fernandez 
  To: Ant Project List (E-mail) 
  Sent: Tuesday, September 26, 2000 11:59 PM
  Subject: Redirecting output and background processes

  here are two more things to my ANT whish list:
  1) add an attribute for <echo> to write to a file. Or have an <writefile> task.
      the idea is to be able to create small files based on the values of different properties.
  2) Add an attribute to the <exec> task to allow the process to run in the background,

      independently of ANT. This will mean to cal a script with "&" in UNIX or use the
      "start" command on Windows. I do not know for other OSs like MacOS, etc.
  Does any one has a good idea on how to achieve (2) or how much is necessary to change on
the script files used by <exec> today?
  Jose Alberto

View raw message