Solved

IzPack - the file version is different from the compiler version

Posted on 2014-02-05
3
714 Views
Last Modified: 2014-03-16
Dear Experts

I am trying to make an installation program using IzPack 5 and I keep getting the error message "the file version is different from the compiler version".

What is wrong? Please help me - I need to have this functionning before next week.

I am using the following xml-file:

<?xml version="1.0" encoding="iso-8859-1" standalone = "yes"?>

<installation version="1.0">

    <!--
       The info section.
       The meaning of the tags should be natural ...
   -->
    <info>
        <appname>UndesertDSS</appname>
        <appversion>1.0</appversion>
        <authors>
            <author name="Jorgen Axelsen" email="jaa@dmu.dk"/>
        </authors>
    </info>

    <!--
       The gui preferences indication.
       Sets the installer window to 640x480. It will not be able to change the size.
   -->
    <guiprefs width= "660" height="480"  resizable="yes">
<modifier key= "allXGap" value="0"/>
<modifier key="allYGap" value="0"/>
<modifier key="useHeadingPanel" value="yes"/>
<modifier key="useButtonIcons" value="yes"/>
<modifier key="useHeadingForSummary" value="yes"/>
<modifier key="headingImageOnLeft" value="yes"/>
<modifier key="headingLineCount" value="1"/>
<modifier key="headingFontSize" value="1.5"/>
<modifier key="headingBackgroundColor" value="0x00ffffff"/>
<modifier key="headingPanelCounter" value="text"/>
<modifier key="headingPanelCounterPos" value="inHeading"/>
</guiprefs>


    <!--
       The locale section.
       Asks here to include the English and French langpacks.
   -->
    <locale>
        <langpack iso3="eng"/>
    </locale>

    <!--
       The resources section.
       The ids must be these ones if you want to use the LicencePanel and/or the InfoPanel.
   -->
    <resources>
        <res src="shortcutSpec.xml" id="shortcutSpec.xml"/>
        <res id="LicencePanel.licence" src="Licence.txt"/>
        <res id="InfoPanel.info" src="Readme.txt"/>
        <res id="TargetPanel.dir" src="defaultInstallDir.txt" />
    </resources>

    <!--
       The panels section.
       We indicate here which panels we want to use. The order will be respected.
   -->
    <panels>
        <panel classname="HelloPanel"/>
        <panel classname="LicencePanel"/>
        <panel classname="DefaultTargetPanel" />
        <panel classname="PacksPanel"/>
        <panel classname="InstallPanel"/>
        <panel classname="ShortcutPanel"/>
        <panel classname="FinishPanel"/>
    </panels>

    <!--
       The packs section.
       We specify here our packs.
   -->
    <packs>
        <pack name="Basics" required="yes">
            <description>The basic files</description>
            <file src="Readme.txt" targetdir="$INSTALL_PATH"/>
            <file src="Licence.txt" targetdir="$INSTALL_PATH"/>
            <file src="UndesertDSS.ico" targetdir="$INSTALL_PATH"/>
            <file src="UndesertDecisionSupport.jar" targetdir="$INSTALL_PATH"/>
            <fileset dir="lib" targetdir="$INSTALL_PATH/lib">
                <include name="**"/>
                </fileset>
            <fileset dir="Ecosystems" targetdir="$INSTALL_PATH/Ecosystems">
                <include name="**"/>
                </fileset>
            <fileset dir="Especes" targetdir="$INSTALL_PATH/Especes">
                <include name="**"/>
                </fileset>
            <fileset dir="ClimateFiles" targetdir="$INSTALL_PATH/ClimateFiles">
                <include name="**"/>
                </fileset>
            <fileset dir="DefaultSolarFiles" targetdir="$INSTALL_PATH/DefaultSolarFiles">
                <include name="**"/>  
            </fileset>
        </pack>
    </packs>
</installation>


best regards
JorgenAxelsen
0
Comment
Question by:JorgenAx
  • 2
3 Comments
 

Author Comment

by:JorgenAx
ID: 39835469
I have found a solution.  the following code did the job:

<izpack:installation version="5.0"
                     xmlns:izpack="http://izpack.org/schema/installation"
                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                     xsi:schemaLocation="http://izpack.org/schema/installation http://izpack.org/schema/5.0/izpack-installation-5.0.xsd">

    <!--
       The info section.
       The meaning of the tags should be natural ...
   -->
    <info>
        <appname>UndesertDSS</appname>
        <appversion>1.0</appversion>
        <authors>
            <author name="Jorgen Axelsen" email="jaa@dmu.dk"/>
        </authors>
        <javaversion>1.6</javaversion>
    </info>

<!--
       The locale section.
       Asks here to include the English and French langpacks.
   -->
    <locale>
        <langpack iso3="eng"/>
    </locale>
    <!--
       The gui preferences indication.
       Sets the installer window to 640x480. It will not be able to change the size.
   -->
    <guiprefs width="640" height="480" resizable="yes"/>
    <laf name="substance">
      <os family="windows" />
      <os family="unix" />
      <param name="variant" value="mist-silver" />
    </laf>
    <laf name="substance">
      <os family="mac" />
      <param name="variant" value="mist-aqua" />
    </laf>
    <modifier key="useHeadingPanel" value="yes" />
    <variables>
        <variable name="DesktopShortcutCheckboxEnabled" value="true"/>
    </variables>
   

    <!--
       The resources section.
       The ids must be these ones if you want to use the LicencePanel and/or the InfoPanel.
   -->
    <resources>
        <res src="shortcutSpec.xml" id="shortcutSpec.xml"/>
        <res id="LicencePanel.licence" src="Licence.txt"/>
        <res id="InfoPanel.info" src="Readme.txt"/>
        <res id="TargetPanel.dir" src="defaultInstallDir.txt" />
    </resources>

    <!--
       The panels section.
       We indicate here which panels we want to use. The order will be respected.
   -->
    <panels>
        <panel classname="HelloPanel"/>
        <panel classname="LicencePanel"/>
        <panel classname="DefaultTargetPanel" />
        <panel classname="PacksPanel"/>
        <panel classname="InstallPanel"/>
        <panel classname="ShortcutPanel"/>
        <panel classname="FinishPanel"/>
    </panels>

    <!--
       The packs section.
       We specify here our packs.
   -->
    <packs>
        <pack name="Basics" required="yes">
            <description>The basic files</description>
            <file src="Readme.txt" targetdir="$INSTALL_PATH"/>
            <file src="Licence.txt" targetdir="$INSTALL_PATH"/>
            <file src="UndesertDSS.ico" targetdir="$INSTALL_PATH"/>
            <file src="UndesertDecisionSupport.jar" targetdir="$INSTALL_PATH"/>
            <fileset dir="lib" targetdir="$INSTALL_PATH/lib">
                <include name="**"/>
                </fileset>
            <fileset dir="Ecosystems" targetdir="$INSTALL_PATH/Ecosystems">
                <include name="**"/>
                </fileset>
            <fileset dir="Especes" targetdir="$INSTALL_PATH/Especes">
                <include name="**"/>
                </fileset>
            <fileset dir="ClimateFiles" targetdir="$INSTALL_PATH/ClimateFiles">
                <include name="**"/>
                </fileset>
            <fileset dir="DefaultSolarFiles" targetdir="$INSTALL_PATH/DefaultSolarFiles">
                <include name="**"/>  
            </fileset>
        </pack>
    </packs>
    <native type="izpack" name="ShellLink.dll"/>
    <native type="3rdparty" name="COIOSHelper.dll" stage="both">
        <os family="windows"/>
    </native>
</izpack:installation>
0
 
LVL 25

Accepted Solution

by:
nickg5 earned 500 total points
ID: 39895156
Good job, glad to hear it.
0
 

Author Comment

by:JorgenAx
ID: 39932384
No comments
0

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Monitor input from a computer is usually nothing special.  In this instance it prevented anyone from using the computer.  This was a preconfiguration that didn't work.
Let’s list some of the technologies that enable smooth teleworking. 
Video by: Tony
This video teaches viewers how to export a project from Adobe Premiere Pro and the various file types involved.
An overview on how to enroll an hourly employee into the employee database and how to give them access into the clock in terminal.

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question