ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Replacing Text In a File with a Property Value
Date Fri, 06 Aug 2004 13:50:43 GMT

I was actually dorking it up. I had gotten the replace task wrong and was 
replacing the source file not the destination. So, after I fixed it, I 
neglected to do a fresh get. Silly me...

FWIW, InstallAnywhere doesn't allow you to pass in variables for grabbing 
the contents of the installer. Locations are hardcoded in the iap_xml 
files. So, you can set up the IA job on a workstation relative to some 
arbitrary path. Then, you can use the replace task during the build to 
change those paths in your iap_xml files. It's not very elegant, but does 
allow you the ability to have platform independent builds with 

Now if only I could get an Open Source alternative to InstallAnywhere...


Erik Hatcher <> 
08/06/2004 03:11 AM
Please respond to
"Ant Users List" <>

"Ant Users List" <>

Re: Replacing Text In a File with a Property Value

Have a look at <copy> with a nested <filterset>.

Also, one of the most special Ant tasks out there is VPPCopy (or its 
companion filter reader):


VPP is a Velocity Pre-Processor - using it for generation from 
templated text files is one of its strong suits.


On Aug 5, 2004, at 11:50 AM, wrote:

> The Install Anywhere task does not allow you to pass in variables to be
> used within the installer creation. So, I have a bunch of iap_xml files
> that have hardcoded install build locations.
> I need these to be dynamic because my build system builds official 
> builds
> in different locations every time. Also, I don't want my builds tied to
> the file system structure.
> So, I'm attempting to replace c:\foo\bar with my current installer 
> build
> directory stored in ${assemble.dir}. However, the replace target will
> explicitly put in ${assemble.dir} instead of c:\real\installer\dir. The
> same thing happens with copy and filterchains.
> How can I tell Ant to use the value stored in ${assemble.dir} and not 
> the
> actual text?
> Thanks,
> Robert

To unsubscribe, e-mail:
For additional commands, e-mail:

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