[izpack-users] How to use the Built in variables?

[Klaus Bartz]

Hi Sagar,
if you mean config files which are used in your program after
installation you can use and it is no problem.
Put the file into a <fileset>, <singelfile> or <file> in your
install.xml.
Additional declare a <parsable> element for the same file in install.xml
like (it's from one of my clients)
   <parsable targetfile="$INSTALL_PATH/bin/StartCustomizingClient"  
type="shell" os="unix"/>
   <parsable targetfile="$INSTALL_PATH/bin/StartCustomizingClient.cmd"  
os="windows"/>
With the type you can determine the variable identifier, good e.g. for
scripts or cmd's. At "shell" the variables are marked as e.g.
%HOST_NAME; the revise will not alter the declared shell vars.

OS determines the operating system where the revise should be performed.
You can use all IzPack variables which are declared at running  
InstallPanel,
not only built in variables.
Sometimes it is better to use the long form of variables
${myvar.includes.specialChars} with brackets.

If you mean config files which are used during installation (e.g.
userInputSpec.xml) the situation is a little bit complicated.


Cheers

Klaus

Am 24.03.2006, 05:09 Uhr, schrieb sagar shah <sagarbs at gmail.com>:

> Hi,
> I want to use the built in variables like, $HOST_NAME, $JAVA_HOME,
> $IP_ADDRESS and replace in my config files. But i dont want to ask user  
> for
> input. Can I directly use them in my xml config files and parse the file
> while the installation so that the values of these variables are
> substituted?
> Please help me out.
> --
> Regards,
> Sagar Shah.
> email : sagarbs at gmail.com
>
>
> __________ NOD32 1.1450 (20060318) Information __________
>
> Diese E-Mail wurde vom NOD32 Antivirus System geprüft
> http://www.nod32.com
>



-- 
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/