Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 64874 invoked by uid 500); 14 Mar 2001 18:01:36 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 64764 invoked from network); 14 Mar 2001 18:01:33 -0000 Message-ID: <3AAFB1FC.48BAC50F@progress.com> Date: Wed, 14 Mar 2001 13:01:33 -0500 From: "Bill Burton" Organization: Progress Software Corporation X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en-US MIME-Version: 1.0 To: ant-user@jakarta.apache.org Subject: Re: InstallAnywhere? References: <462F323275D6D311BA0200805F356C52EC6E50@lgcadev001.zycor.lgc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi Steve, Steve Donie wrote: > > I have started using InstallAnywhere enterprise (just the evaluation version > so far). I have some issues with it so far - I haven't been able to figure > out (in the day or so that I've used it) how to get it to use relative > pathnames (I hate to hard code paths!). But otherwise, it seems to be > working fine. Here is a snippet of my build.xml that does the work: Regrettably, InstallAnywhere 3.5 doesn't support relative paths. When you save a project in the IDE, it creates a file with the same name but with the suffix "Backup.iap." In your case, that would be "tahoeBackup.iap." This is a Java source file version of the project. You could then replace whatever values you need and then use this modified project file for the build. Better yet, you could write an Ant task to do this on the fly :) . > I also currently have the path to the InstallAnywhere classes/jars/zips > hardcoded, which I also don't like. Works for now. For this, just specify a property like: then use ${ia.home} everywhere it's required. -Bill > > > > > > > > > > > > > > > > > >