Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • input: the XML installation file. The installation can be specified as an external file, or embedded using a config child element.
  • output: the output jar installer file
  • installerType: (optional), possible values: standard or web. If web, the <webdir> attribute must be specified in the input file. Used to force creation of a standard installer when the <webdir> attribute has been used.
  • inheritAll: (optional, boolean). If true all properties defined in the ant build process are transmitted to izpack parser for substitution. 

  • baseDir: the base directory to resolve the relative paths
  • izPackDir: the IzPack home directory (the target directory when executing the izpack-dist.jar)
  • mkdirs: whether to automatically create the parent directories of the installer jar to be built.
  • inheritAll: If true, pass all Ant properties to IzPack. Defaults to false.
  • compression: The type of compression to set for pack compression.
  • compressionLevel: The compression level if compression is set to true.

Nested elements:

  • <config>
    Used for embedding the contents of install.xml as CDATA directly to the build file (see the example in the section below) 
  • <property>
    Add a property to the build visible only to the IzPack task. The Syntax is the same like for defining properties in Ant.
  • <propertyset>
    Add a property set to the build visible only to the IzPack task. The Syntax is the same like for defining a propertyset in Ant. 

Here is how the Ant build file may look like:

...

It builds an executable installer setup.jar in the working directory.

Anchor
Embedding

...

contents as CDATA
Embedding

...

contents as CDATA
Embedding the installation file contents

...

as CDATA

Instead of using the 'input' attribute to specify an external installation document, you can embed the installation config as a child of the IzPack task using a config child element with a CDATA section. For example:

Code Block
languagexml
titleExample
<property name="jboss.home.url" value="http://www.jboss.com/" />

...


...

...

 

 
<!-- Call IzPack with an embedded install using the config element -->

...


<IzPack output="${dist.dir}/IzPack-install.jar"

...


        installerType="standard"

...


        basedir="${dist.dir}"

...


        inheritAll="true"

...


        IzPackDir="${dist.dir}/">

...


        <config><![CDATA[

...


<installation version="1.0">

...

   <info>
      <appname>JBossAS</appname>
      <appversion>4.0.2</appversion>

...


   <info>
      <appname>JBossAS</appname>
      <appversion>4.0.2</appversion>
      <appsubpath>jboss-4.0.

...

2</appsubpath>

...

      <authors>

...


      <authors>
         <author name="JBoss Inc." email="sales@jboss.com"/>

...


      </authors>

...


      <url>@{jboss.home.url}</url>

...

      <javaversion>1.4</javaversion>

...


      <javaversion>1.4</javaversion>
   </info>

...


...

...


        ]]></config>

...


</IzPack>


Property references of the form

...