Property changes on: bin\langpacks\installer\fa.xml ___________________________________________________________________ Name: svn:eol-style + native Index: bin/langpacks/installer/glg.xml =================================================================== --- bin/langpacks/installer/glg.xml (revision 2109) +++ bin/langpacks/installer/glg.xml (working copy) @@ -200,7 +200,7 @@ - + Property changes on: bin\langpacks\installer\glg.xml ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Index: bin/langpacks/installer/ind.xml =================================================================== --- bin/langpacks/installer/ind.xml (revision 2109) +++ bin/langpacks/installer/ind.xml (working copy) @@ -1,9 +1,9 @@ - - - + + + - + @@ -25,267 +25,267 @@ - - + + - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + txt="Direktori tersebut sudah ada! Apakah Anda yakin untuk melakukan pemasangan ke sana dan kemungkinan menimpa arsip-arsip yang telah ada?" /> - + txt="Anda belum menspesifikasi lokasi tujuan! Apakah betul?" /> + + txt="Arsip ini bukan direktori! Silakan pilih sebuah direktori!" /> - - - - - - - - - - - - - - + txt="Direktori ini tidak dapat ditulisi! Silakan pilih direktori lain!" /> + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - + txt="Ruang cakram yang diperlukan untuk pemasangan melebihi ruang cakram yang tersedia." /> + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + txt="Gunakan naskah ini untuk mengulangi pemasangan ini ke komputer lain." /> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Property changes on: bin\langpacks\installer\ind.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: bin\langpacks\installer\tur.xml ___________________________________________________________________ Name: svn:executable - * Property changes on: sample\listener\install.xml ___________________________________________________________________ Name: svn:executable - * Property changes on: sample\listener\test1\ShouldNotSeenWith_ls.txt ___________________________________________________________________ Name: svn:executable - * Property changes on: sample\listener\test2\ShouldSeenWith_ls.txt ___________________________________________________________________ Name: svn:executable - * Property changes on: sample\src\myCompany\tools\install\listener\ChmodCompilerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: sample\src\myCompany\tools\install\listener\ChmodInstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\dist-files\conditions.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\dist-files\RegistrySpec.xml ___________________________________________________________________ Name: svn:executable - * Property changes on: src\doc-reST\advanced-features.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\apache-license.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\cc-license.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\cookbooks.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\creating-panels.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\custom-actions.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\desktop-shortcuts.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\getting-started.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\html4css1.css ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\index.txt ___________________________________________________________________ Name: svn:eol-style + native Index: src/doc-reST/installation-files.txt =================================================================== --- src/doc-reST/installation-files.txt (revision 2109) +++ src/doc-reST/installation-files.txt (working copy) @@ -1,200 +1,200 @@ -Writing Installation XML Files -============================== - -.. include:: include-top.inc - -What You Need -------------- - - -Your editor -''''''''''' - -In order to write your XML installation files, you just need a plain text -editor. Of course it's always easier to work with color coded text, so you -might rather want to work with a text editor having such a feature. Here is a -list of free editors that work well : - -- Jext : http://www.jext.org/ -- JEdit : http://www.jedit.org/ -- classics like Vim and (X)Emacs. - -If you are a developer and tend to write your own patches, extension or -features to IzPack sources, or, if you wish to debug your compilation, -installation and uninstallation, we recommend these IDE: - -- IntelliJ IDEA : http://www.jetbrains.com/idea/ -- Eclipse : http://www.eclipse.org/ -- Netbeans : http://www.netbeans.org/ - -For the first one, JetBrains has granted us an Open Source License. All -project members can ask the Licence Key to one of the project manager. - -The other ones are well know open source projects (Just like us :-)). We provide -a tutorial on how to develop/debug IzPack using Eclipse in the chapter -''Getting Started > How to develop and debug IpPack using Eclipse'' - - -Writing XML -''''''''''' - -Though you might not know much about XML, you have certainly heard about it. -If you know XML you can skip this subsection as we will briefly present how -to use XML. - - -XML is a markup language, really close to HTML. If you've ever worked with -HTML the transition will be fast. However there are a few little things to -know. The markups used in XML have the following form : ````. Each -markup has to be closed somewhere with its ending tag : ````. Each -tag can contain text and other markups. If a markup does not contain -anything, it is just reported once : ````. A markup can contain -attributes like : ````. Here is a sample -of a valid XML structure : - -:: - - -
- - This is the text of the paragraph number 1. It is available - for the very low - price of 1 000 000. - -
-
- xxx -
- - - -You should be aware of the following common mistakes : - -- markups **are** case sensitive : ```` is different from - ````. -- you **must** close the markups in the same order as you create them : - ``(...)`` is right but `` (...)`` is - not. - -Also, an XML file must start with the following header : -````. The only -thing you should modify is the encoding (put here the one your text editor -saves your files to). The `` standalone`` attribute is not very important for -us. - - -This (brief !) introduction to XML was just meant to enable you to write your -installation specification. For a better introduction there are plenty of -books and articles/tutorials dealing with XML on the Internet, in book -stores, in magazines and so on. - -Variable Substitution ---------------------- - -During the installation process IzPack can substitute variables in various -places with real values. Obvious targets for variable substitution are -resource files and launch scripts, however you will notice many more places -where it is more powerful to use variables rather then hard coded values. -Wherever variables can be used it will be explained in the documentation. - - -There are three types of variables: - -- Built-In variables. These are implemented in IzPack and are all - dynamic in nature. This means that the value of each variable depends on - local conditions on the target system. -- Environment variables. These are provided by the operating system the - installer is run on. -- Variables that you can define. You also define the value, which is - fixed for a given installation file. - -You define your own variables in the installation XML file with the -```` tag. How to do this is explained in detail later in this -chapter. - - -**Please note** that when using variables they must always appear with a -'``$``' sign as the first character, even though they are not defined this -way. - - - -The Built-In Variables ----------------------- - -The following variables are built-in : - -- ``$INSTALL_PATH`` : the installation path on the target system, as - chosen by the user -- ``$APPLICATIONS_DEFAULT_ROOT`` : the default path for applications -- ``$JAVA_HOME`` : the JavaTM virtual machine home path -- ``$CLASS_PATH`` : the Class Path used mainly for Java Applications -- ``$USER_HOME`` : the user's home directory path -- ``$USER_name`` : the user name -- ``$APP_name`` : the application name -- ``$APP_URL`` : the application URL -- ``$APP_VER`` : the application version -- ``$ISO3_LANG`` : the ISO3 language code of the selected langpack. -- ``$IP_ADDRESS`` : the IP Address of the local machine. -- ``$HOST_NAME`` : the HostName of the local machine. -- ``$FILE_SEPARATOR`` : the file separator on the installation system -- ``$DesktopShortcutCheckboxEnabled`` : When set to true, it - automatically checks the "Create Desktop Shortcuts" button. To see how to - use it, go to `The Variables Element ```` Be careful this - variable is case sensitve ! -- ``$InstallerFrame.logfilePath`` : The path to the install log. This - file contains the paths of all installed files. If set to "default" then - the "$INSTALL_PATH/Uninstaller/install.log" path will be used. To see how - to use it, go to `The Variables Element ````. If this - variable is not set, no install.log will be created. - - -Environment Variables ---------------------- - -Environment variables can be accessed via the syntax ``${ENV[variable]}``. -The curly braces are mandatory. Note that variable names are case-sensitive -and usually in UPPER CASE. - -Example: To get the value of the OS environment variable "CATALINA_HOME", use -``${ENV[CATALINA_HOME]}``. - - -Dynamic Variables ------------------ - -Dynamic variables can be defined in the installation XML with the ```` tag inside -the ```` element. The value of dynamic variables will be evaluated every time a panel -is switched, i.e. between the panels. Dynamic variables can have a condition which will be evaluated -first. If it's true, the value would be assigned, otherwise nothing happens to the variable. - -Example: To change a certain directory based on user input, use the following -```` -The condition has userinput has to be specified in the condition section of installation XML. - -Parse Types ------------ - -Parse types apply only when replacing variables in text files. At places -where it might be necessary to specify a parse type, the documentation will -mention this. Depending on the parse type, IzPack will handle special cases --such as escaping control characters- correctly. The following parse types -are available: - -- ``plain`` - use this type for plain text files, where no special - substitution rules apply. All variables will be replaced with their - respective values as is. -- ``javaprop`` - use this type if the substitution happens in a Java - properties file. Individual variables might be modified to function - properly within the context of Java property files. -- ``xml`` - use this type if the substitution happens in a XML file. - Individual variables might be modified to function properly within the - context of XML files. -- ``shell`` - use this type if the substitution happens in a shell - script. Because shell scripts use ``$variable`` themselves, an - alternative variable marker is used: ``%variable`` or ``%{variable}``. +Writing Installation XML Files +============================== + +.. include:: include-top.inc + +What You Need +------------- + + +Your editor +''''''''''' + +In order to write your XML installation files, you just need a plain text +editor. Of course it's always easier to work with color coded text, so you +might rather want to work with a text editor having such a feature. Here is a +list of free editors that work well : + +- Jext : http://www.jext.org/ +- JEdit : http://www.jedit.org/ +- classics like Vim and (X)Emacs. + +If you are a developer and tend to write your own patches, extension or +features to IzPack sources, or, if you wish to debug your compilation, +installation and uninstallation, we recommend these IDE: + +- IntelliJ IDEA : http://www.jetbrains.com/idea/ +- Eclipse : http://www.eclipse.org/ +- Netbeans : http://www.netbeans.org/ + +For the first one, JetBrains has granted us an Open Source License. All +project members can ask the Licence Key to one of the project manager. + +The other ones are well know open source projects (Just like us :-)). We provide +a tutorial on how to develop/debug IzPack using Eclipse in the chapter +''Getting Started > How to develop and debug IpPack using Eclipse'' + + +Writing XML +''''''''''' + +Though you might not know much about XML, you have certainly heard about it. +If you know XML you can skip this subsection as we will briefly present how +to use XML. + + +XML is a markup language, really close to HTML. If you've ever worked with +HTML the transition will be fast. However there are a few little things to +know. The markups used in XML have the following form : ````. Each +markup has to be closed somewhere with its ending tag : ````. Each +tag can contain text and other markups. If a markup does not contain +anything, it is just reported once : ````. A markup can contain +attributes like : ````. Here is a sample +of a valid XML structure : + +:: + + +
+ + This is the text of the paragraph number 1. It is available + for the very low + price of 1 000 000. + +
+
+ xxx +
+ + + +You should be aware of the following common mistakes : + +- markups **are** case sensitive : ```` is different from + ````. +- you **must** close the markups in the same order as you create them : + ``(...)`` is right but `` (...)`` is + not. + +Also, an XML file must start with the following header : +````. The only +thing you should modify is the encoding (put here the one your text editor +saves your files to). The `` standalone`` attribute is not very important for +us. + + +This (brief !) introduction to XML was just meant to enable you to write your +installation specification. For a better introduction there are plenty of +books and articles/tutorials dealing with XML on the Internet, in book +stores, in magazines and so on. + +Variable Substitution +--------------------- + +During the installation process IzPack can substitute variables in various +places with real values. Obvious targets for variable substitution are +resource files and launch scripts, however you will notice many more places +where it is more powerful to use variables rather then hard coded values. +Wherever variables can be used it will be explained in the documentation. + + +There are three types of variables: + +- Built-In variables. These are implemented in IzPack and are all + dynamic in nature. This means that the value of each variable depends on + local conditions on the target system. +- Environment variables. These are provided by the operating system the + installer is run on. +- Variables that you can define. You also define the value, which is + fixed for a given installation file. + +You define your own variables in the installation XML file with the +```` tag. How to do this is explained in detail later in this +chapter. + + +**Please note** that when using variables they must always appear with a +'``$``' sign as the first character, even though they are not defined this +way. + + + +The Built-In Variables +---------------------- + +The following variables are built-in : + +- ``$INSTALL_PATH`` : the installation path on the target system, as + chosen by the user +- ``$APPLICATIONS_DEFAULT_ROOT`` : the default path for applications +- ``$JAVA_HOME`` : the JavaTM virtual machine home path +- ``$CLASS_PATH`` : the Class Path used mainly for Java Applications +- ``$USER_HOME`` : the user's home directory path +- ``$USER_name`` : the user name +- ``$APP_name`` : the application name +- ``$APP_URL`` : the application URL +- ``$APP_VER`` : the application version +- ``$ISO3_LANG`` : the ISO3 language code of the selected langpack. +- ``$IP_ADDRESS`` : the IP Address of the local machine. +- ``$HOST_NAME`` : the HostName of the local machine. +- ``$FILE_SEPARATOR`` : the file separator on the installation system +- ``$DesktopShortcutCheckboxEnabled`` : When set to true, it + automatically checks the "Create Desktop Shortcuts" button. To see how to + use it, go to `The Variables Element ```` Be careful this + variable is case sensitve ! +- ``$InstallerFrame.logfilePath`` : The path to the install log. This + file contains the paths of all installed files. If set to "default" then + the "$INSTALL_PATH/Uninstaller/install.log" path will be used. To see how + to use it, go to `The Variables Element ````. If this + variable is not set, no install.log will be created. + + +Environment Variables +--------------------- + +Environment variables can be accessed via the syntax ``${ENV[variable]}``. +The curly braces are mandatory. Note that variable names are case-sensitive +and usually in UPPER CASE. + +Example: To get the value of the OS environment variable "CATALINA_HOME", use +``${ENV[CATALINA_HOME]}``. + + +Dynamic Variables +----------------- + +Dynamic variables can be defined in the installation XML with the ```` tag inside +the ```` element. The value of dynamic variables will be evaluated every time a panel +is switched, i.e. between the panels. Dynamic variables can have a condition which will be evaluated +first. If it's true, the value would be assigned, otherwise nothing happens to the variable. + +Example: To change a certain directory based on user input, use the following +```` +The condition has userinput has to be specified in the condition section of installation XML. + +Parse Types +----------- + +Parse types apply only when replacing variables in text files. At places +where it might be necessary to specify a parse type, the documentation will +mention this. Depending on the parse type, IzPack will handle special cases +-such as escaping control characters- correctly. The following parse types +are available: + +- ``plain`` - use this type for plain text files, where no special + substitution rules apply. All variables will be replaced with their + respective values as is. +- ``javaprop`` - use this type if the substitution happens in a Java + properties file. Individual variables might be modified to function + properly within the context of Java property files. +- ``xml`` - use this type if the substitution happens in a XML file. + Individual variables might be modified to function properly within the + context of XML files. +- ``shell`` - use this type if the substitution happens in a shell + script. Because shell scripts use ``$variable`` themselves, an + alternative variable marker is used: ``%variable`` or ``%{variable}``. - ``at`` - use this type if the substitution must occure on files - where paramters are marked with leading AT characters. + where paramters are marked with leading AT characters. The example: ``@variable``. - ``ant`` - use this type if the substitution must occure on files where parameters are surrounded with AT characters (similar to ANT @@ -211,963 +211,963 @@ then you must use braces, and the above example should look like: ``${major-version}.${minor-version}``. - - -The IzPack Elements -------------------- - -*When writing your installer XML files, it's a good idea to have a look at -the iZPACK installation DTD*. - - - - -The Root Element ```` -'''''''''''''''''''''''''''''''''''' - -The root element of an installation is ````. It takes one -required attribute : ``version``. The attribute defines the version of the -XML file layout and is used by the compiler to identify if it is compatible -with the XML file. This should be set to **1.0** for the moment. - - -The Information Element ```` -''''''''''''''''''''''''''''''''''' - -This element is used to specify some general information for the installer. -It contains the following elements : - -- ```` : the application name -- ```` : the application version -- ```` : the subpath for the default of the installation - path. A variable substitution and a maskable slash-backslash conversion - will be done. If this tag is not defined, the application name will be - used instead. -- ```` : the application official website url -- ```` : specifies the author(s) of the application. It must - contain at least one ```` element whose attributes are : - - - ``name`` : the author's name - - ``email`` : the author's email - -- ```` : specifies whether to create an uninstaller after - installation, and which name to use for it. This tag has the ``write`` - attribute, with default value `` yes``. If this tag is not specified, the - uninstaller will still be written. The ``name`` attribute can be used to - change the default name of the generated uninstaller, *i.e.* `` - uninstaller.jar``. -- ```` : specifies the minimum version of Java required to - install your program. Values can be ``1.2``, ``1.2.2``, ``1.4``, etc. The - test is a lexical comparison against the ``java.version`` System property - on the install machine. -- ````: (yes or no) specifies wether a JDK is required for the software - to be installed and executed. If not, then the user will be informed and given the - option to still proceed with the installation process or not. -- ```` : Causes a ''web installer'' to be created, and - specifies the URL packages are retrieved from at install time. The - content of the tag must be a properly formed URL. -- ```` : specifies the path for the logfile of the - `SummaryLoggerInstallerListener`. -- ```` : (yes or no) specifies if the file .installinformation should - be written which includes the information about installed packs. The default if not specified is yes. - -Here is an example of a typical ```` section : - - -:: - - - Super extractor - 2.1 beta 6 - myCompany/SExtractor - http://www.superextractor.com/ - - - - - 1.2 - - -The Packaging Element ```` -'''''''''''''''''''''''''''''''''''''' - -This element allows to specify packaging options. If not specified, the default will be to create an all in one -installer. This element will usually be used to create an installer which spans over multiple volumes, -e.g. the output will be two CDs. The packaging-element contains the following elements: - -- ```` : specifies options used by the packager. The packager tag has the ``class`` attribute, - which specifys the class to use for packaging. Currently two implementations - are available (com.izforge.izpack.compiler.Packager, com.izforge.izpack.compiler.MultiVolumePackager). - The packager-element can contain the ```` element which can have different attributes for the different - implementations of packagers. For the MultiVolumePackager, it can have the following attributes: - - - ``volumesize``: the size of the volumes - - ``firstvolumefreespace``: free space on the first volume used for the installer jar and additional resources like - readme-files etc. - - -- ```` : specifies which unpacker class should be used. Currently there are two unpacker implementations - (com.izforge.izpack.compiler.UnPacker, com.izforge.izpack.compiler.MultiVolumeUnPacker). - -Here's an example how to specify an installer which will create multiple volumes. In this example the volumes shall be -CDs with 650 megabytes. There will be an additional free space of 150 megabytes on the first volume. This will result in -the creation of an installer.jar and multiple installer.pak* files. The installer.jar plus installer.pak plus the additional -resources have to be copied on the first volume, each installer.pak. on several volumes. - -:: - - - - - - - - - -The Variables Element ```` -'''''''''''''''''''''''''''''''''''''' - -This element allows you to define variables for the variables substitution -system. Some variables are built-in, such as ``$INSTALL_PATH`` (which is the -installation path chosen by the user). When you define a set of variables, -you just have to place as many ```` tags in the file as needed. If -you define a variable named ``VERSION`` you need to type $VERSION in the -files to parse. The variable substitutor will then replace it with the -correct value. One ```` tag take the following attributes : - -- ``name`` : the variable name -- ``value`` : the variable value - -Here's a sample ```` section : - - -:: - - - - - - - -Here's a precise sample on how to use desktopshortcutcheckboxenabled and -InstallerFrame.logfilePath variables: - - -:: - - - - - - - - - - -The dynamic Variables Element ```` -'''''''''''''''''''''''''''''''''''''''''''''''''''' - -This element allows you to define dynamic variables for the variables substitution -system. In contrast to the static ```` tags -in the file as needed. Normally you would use the condition attribute to specify, when -a certain value will be set. - -One ```` tag take the following attributes : - -- ``name`` : the variable name -- ``value`` : the variable value -- ``condition`` : a condition for this variable, which has to be true to set the value - -Here's a sample ```` section : - - -:: - - - - - - - - -The Conditions Element ```` -'''''''''''''''''''''''''''''''''''''''' - -This element allows you to define conditions which can be used to dynamically change the installer, -e.g. the panels shown, the variables set, files parsed, files -executed and much more. When you define a condition it will get a type and an id. The id has to be unique. Conditions can be referenced -based on this id (e.g. with the ``RefCondition``). - -There are several built-in types of conditions. At the time of writing this, Izpack has the following built-in types: - -- ``VariableCondition``: a condition based on the value of a certain variable -- ``PackSelectionCondition``: a condition based on a pack selected for installation -- ``JavaCondition``: a condition based on a static java field or method. - -There are also boolean types to combine more than one condition: - -- ``AndCondition``: both conditions have to be true -- ``OrCondition``: only one of both conditions has to be true -- ``XOrCondition``: one condition has to be true, the other one has to be false -- ``NotCondition``: the condition has to be false - -When you define a set of conditions, you just have to write as many ```` tags as you like. A -condition can take the following attributes: - -- ``type``: the type of the condition. For built-in types, this is the lowercase portion of the condition class - name without condition appended (variable,packselection,java, ...). Custom condition types should be - referenced by the full qualified class name, e.g. de.dr.rules.MyCoolCondition. -- ``id``: the id of the condition. This will be used to refer to this conditions in other elements - -The condition element can have several child elements depending on the type of this conditions. E.g. the VariableCondition -has a name and value child element to specify, which variable should have a certain value to fullfil this condition. - -This is an example which defines four conditions, two VariableConditions, a JavaCondition and a AndCondition which will -refer to two of the first conditions. - -:: - - - - setup.type - standard - - - setup.type - expert - - - - com.izforge.izpack.util.OsVersion - IS_WINDOWS - - true - - - - - - - -Note, from IzPack 3.11 on normally, you don't have to define the compound conditions because you can use a simple -expression language. The language has the following operators: - -- ``+``: an operator for the Andcondition -- ``|``: an operator for the OrCondition -- ``\``: an operator for the XOrCondition -- ``!``: an operator for the NotCondition - -Neverthless if you define really complex conditions it's much easier to define them using the xml structure. - -More types of conditions can be defined by inheriting com.izforge.izpack.Condition class. - - -The GUI Preferences Element ```` -''''''''''''''''''''''''''''''''''''''''''' - -This element allows you to set the behavior of your installer GUI. This -information will not have any effect on the command-line installers that will -be available in future versions of iZPACK . The arguments to specify are : - -- ``resizable`` : takes ``yes`` or ``no`` and indicates whether the - window size can be changed or not. -- ``width`` : sets the initial window width -- ``height`` : sets the initial window height. - -Here's a sample : - -:: - - - - -Starting from IzPack 3.6, the look and feel can be specified in this section -on a per-OS basis. For instance you can use the native look and feels on -Win32 and OS X but use a third-party one on Unix-like platforms. To do that, -you have to add some children to the ``guiprefs`` tag: - -- ``laf``: the tag that specifies a look and feel. It has a ``name`` - parameter that defines the look and feel name. -- Each ``laf`` element needs at least one ``os`` tag, specified like in - the other parts of the specification that support this tag. -- Like you can add ``os`` elements, you can add any number of ``param`` - elements to customize a look and feel. A ``param`` elements has two - attribues: ``name`` and `` value``. - -The available look and feels are: - -- Kunststoff: ``kunststoff`` -- Liquid: ``liquid`` -- Metouia: ``metouia`` -- JGoodies Looks: ``looks`` -- Substance: ``substance`` - -If you don't specify a look and feel for a particular operating system, then -the default native one will be used: Windows on Windows, Aqua on Mac OS X and -Metal on the Unix-like variants. - - -The *Liquid Look and Feel* supports the following parameters: - -- ``decorate.frames``: ``yes`` means that it will render the frames in - Liquid style -- ``decorate.dialogs``: ``yes`` means that it will render the dialogs - in Liquid style - -The *JGoodies Looks* look and feel can be specified by using the ``variant`` -parameters. The values can be one of: - -- ``windows``: use the Windows look -- ``plastic``: use the basic Plastic look -- ``plastic3D``: use the Plastic 3D look -- ``plasticXP``: use the Plastic XP look (default). - -Here is a small sample: - -:: - - - - - - - - - - - - -The *Substance* look and feel *toned-down* themes can be specified using the -``variant`` parameter, with the value being one of: ``business, business- -blue, business-black, creme, sahara, moderate, officesilver``. We have -reduced the choice to the toned-down themes since they are the only ones to -actually look decent (the other families colors are way too saturated). -Please consult https://substance.dev.java.net/docs/skins/toneddown.html -for a gallery of the different toned-down themes. - -Starting from IzPack 3.7, some characteristics can be customized with the -```` tag. There is a separate description in the `Advanced -Features` chapter paragraph `Modifying the GUI`. - - - -The Localization Element ```` -'''''''''''''''''''''''''''''''''''''' - -This element is used to specify the language packs (langpacks) that you want -to use for your installer. You must set one ```` markup per -language. This markup takes the `` iso3`` parameter which specifies the iso3 -language code. - - -Here's a sample : - - -:: - - - - - - - - -The supported ISO3 codes are : - -========= ============================ -ISO3 code Language -========= ============================ -cat Catalunyan -chn Chinese -cze Czech -dan Danish -glg Galician -deu German -eng English -fin Finnish -fra French -hun Hungarian -ita Italian -jpn Japanese -mys Malaysian -ned Nederlands -nor Norwegian -pol Polnish -por Portuguese (Brazilian) -rom Romanian -rus Russian -scg Serbian -spa Spanish -svk Slovakian -swe Swedish -ukr Ukrainian -========= ============================ - - - -The Resources Element ```` -'''''''''''''''''''''''''''''''''''''' - -Several panels, such as the license panel and the shortcut panel, require -additional data to perform their task. This data is supplied in the form of -resources. This section describes how to specify them. Take a look at each -panel description to see if it might need any resources. Currently, no checks -are made to ensure resources needed by any panel have been included. The `` -`` element is not required, and no ```` elements are required -within. -The ```` element is the only element besides the ```` -element that is taken into consideration in referenced pack-files (see -````` element`_ for more info) - - -You have to set one ```` markup for each resource. Here are the -attributes to specify : - -- ``src`` : the path to the resource file which can be named freely of - course (for instance ``my-picture.jpg``). -- ``id`` : the resource id, depending on the needs of a particular - panel -- ``parse`` : takes ``yes`` or ``no`` (default is ``no``) - used to - specify whether the resource must be parsed at the installer compilation - time. For instance you could set the application version in a readme file - used by ``InfoPanel``. -- ``type`` : specifies the parse type. This makes sense only for a text - resource - the default is ``plain``, other values are ``javaprop, xml`` - (Java properties file and XML files) -- ``encoding`` : specifies the resource encoding if the receiver needs - to know. This makes sense only for a text resource. - -Here's a sample : - -:: - - - - - - - -The Panels Element ```` -''''''''''''''''''''''''''''''''' - -Here you tell the compiler which panels you want to use. They will appear in -the installer in the order in which they are listed in your XML installation -file. Take a look at the different panels in order to find the ones you need. -The ```` markup takes the following attributes: - -- ``classname``: which is the classname of the panel. -- ``id``: an identifier for a panel which can be used e.g. for referencing in userinput panel definitions. -- ``condition``: an id of a condition which has to be fullfilled to show this panel - - -Here's a sample : - -:: - - - - - - - - - - - -The Packs Element ```` -''''''''''''''''''''''''''''''' - -This is a crucial section as it is used to specify the files that need to be -installed. The ```` section consists of several ```` and -```` tags. - -The ```` takes the following attributes : - -- ``name``: the pack name -- ``required``: takes ``yes`` or ``no`` and specifies whether the pack - is optional or not. -- ``os``: optional attribute that lets you make the pack targeted to a - specific *operating system*, for instance ``unix``, ``mac`` and so on. -- ``preselected``: optional attribute that lets you choose whether the - pack is by default selected for installation or not. Possible values are - ``yes`` and ``no``. A pack which is not preselected needs to be - explicitly selected by the user during installation to get installed. -- ``loose``: can be used so that the files are not located in the - installer Jar. The possible values are ``true`` or ``false``, the default - beeing ``false``. The author of this feature needed to put his - application on a CD so that the users could run it directly from this - media. However, he also wanted to offer them the possibility to install - the software localy. Enabling this feature will make IzPack take the - files on disk instead of from the installer. *Please make sure that your - relative files paths are correct !* -- ``id``: this attribute is used to give a unique id to the pack to be - used for internationalization. -- ``packImgId``: this attribute is used to reference a unique resource - that represents the pack's image for the ImgPacksPanel. The resource - should be defined in the ```` element of the installation XML - using the same value for the ``id`` attribute of the ```` element. -- ``condition``: an id of a condition which has to be fullfilled to install this - package. - -The ```` takes only one attribute ``file``, which contains the -relative path (from the installation compiler) to an externally defined -packs-definition. This external packs definition is a regular IzPack -installation XML. However the only elements that are used from that XML file -are the ```` and the ```` elements. This enables a model in -which a single developer is responsible for maintaining the packs and -resources related to the development-package assigned to him. The main -install XML references these xml-files to avoid synchronization efforts -between the central installation XML and the developer-maintained installer -XMLs. - -Internationalization of the PacksPanel -''''''''''''''''''''''''''''''''''''''' - -In order to provide internationalization for the PacksPanel, so that your -users can be presented with a different name and description for each -language you support, you have to create a file named ``packsLang.xml_xyz`` -where ``xyz`` is the ISO3 code of the language in lowercase. Please be aware -that case is significant. This file has to be inserted in the resources -section of `` install.xml`` with the ``id`` and ``src`` attributes set at the -name of the file. The format of these files is identical with the -distribution langpack files located at `` -$IZPACK_HOME/bin/langpacks/installer``. For the name of the panel you just -use the pack ``id`` as the txt ``id``. For the description you use the pack -``id`` suffixed with ``.description``. - -The following sections describe the tags available for a ```` section. - - -```` - pack description -''''''''''''''''''''''''''''''''''''' - -The contents of the ```` tag describe the pack contents. This -description is displayed if the user highlights the pack during installation. - - -```` - pack dependencies -'''''''''''''''''''''''''''''''''' - -This can be used to make this pack selectable only to be installed only if -some other is selected to be installed. The pack can depend on more than one -by specifying more than one `` `` elements. -Circular depedencies are not supported and the compiler reports an error if -one occurs. - -This tag takes the following attribute: - -- ``packname``: The name of the pack that it depends on - - -```` - OS restrictions -''''''''''''''''''''''''''' - -It is possible to restrict a panel to a certain list of operating systems. -This tag takes the following attributes: - -- ``family``: unix, windows or mac -- ``name``: the exact OS name (ie Windows, Linux, ...) -- ``version``: the exact OS version (see the JVM ``os.version`` - property) -- ``arch``: the machine architecture (see the JVM ``os.arch`` - property). - - -```` -'''''''''''''''''' - -This feature can update an already installed package, therefore removing -superfluous files after installation. Here's how this feature author (Tino -Schwarze) described it on the IzPack development mailing-list: - -> Each pack can now specify an ```` tag. It supports a subset of -ant fileset syntax, e.g.: - -:: - - - - `` : will include ``lib`` and the - subdirectories of ``lib`` -- ```` : will exclude any file in any - directory starting from the base path ending by ``.java`` -- ```` : will include all the files ending - by ``.jar`` in ``lib`` -- ```` : will exclude any file in any - subdirectory starting from ``lib`` whose name contains ``FOO``. - -There area set of definitions that are excluded by default file-sets, just as -in Ant. IzPack defaults to the Ant list of default excludes. There is -currently no equivalent to the task. Default excludes are: - -:: - - **/*\~{} - **/\#*\# - **/.\#* - **/%*% - **/.\_* - **/CVS - **/CVS/** - **/.cvsignore - **/SCCS - **/SCCS/** - **/vssver.scc - **/.svn - **/.svn/** - **/.DS\_Store - - -A ```` tag can also be specified for customizing. - - -```` - parse a file after installation -'''''''''''''''''''''''''''''''''''''''''''''''''' - -Files specified by ```` are parsed after installation and may have -variables substituted. - -- ``targetfile`` : the file to parse, could be something like - ``$INSTALL_PATH/bin/launch-script.sh`` - A slash will be changed to the system dependant path separator (e.g. to a - backslash on Windows) only if no backslash masks the slash. -- ``type`` : specifies the type (same as for the resources) - the - default is ``plain`` -- ``encoding`` : specifies the file encoding -- ``os``: specifies the operating system, works like for ```` -- ``condition``: an id of a condition which has to be fullfilled to parse this file - - -```` - mark file executable or execute it -''''''''''''''''''''''''''''''''''''''''''''''''''''''' - -The ```` tag is a very useful thing if you need to execute -something during the installation process. It can also be used to set the -executable flag on Unix-like systems. Here are the attributes : - -- ``targetfile`` : the file to run, could be something like - ``$INSTALL_PATH/bin/launch-script.sh`` - Slashes are handled special (see attribute ``targetfile`` of tag - ````). -- ``class`` : If the executable is a jar file, this is the class to run - for a JavaTM program -- ``type`` : ``bin`` or ``jar`` (the default is ``bin``) -- ``stage`` : specifies when to launch : ``postinstall`` is just after - the installation is done, ``never`` will never launch it (useful to set - the +x flag on Unix). ``uninstall`` will launch the executable when the - application is uninstalled. The executable is executed before any files - are deleted. ``never`` is the default value. -- ``failure`` : specifies what to do when an error occurs : ``abort`` - will abort the installation process, ``ask`` (default) will ask the user - what to do and ``warn`` will just tell the user that something is wrong -- ``os``: specifies the operating system, works like for ```` -- ``keep`` : specifies whether the file will be kept after execution. - The default is to delete the file after is has been executed. This can be - changed by specifying ``keep="true"``. -- ``condition``: an id of a condition which has to be fullfilled to execute this file - -A ```` tag can also be specified in order to pass arguments to the -executable: - -- ````: passes the argument specified in the ``value`` attribute. - Slashes are handled special (see attribute ``targetfile`` of tag - ````. - - - -```` - make a file OS-dependent -'''''''''''''''''''''''''''''''''''''''''''''''''' - -The ```` tag can be used inside the ````, ````, -````, ````, ```` tags to restrict it's -effect to a specific operating system family, architecture or version: - -- ``family``: ``unix, windows, mac`` to specify the operating system - family -- ``name``: the operating system name -- ``version``: the operating system version -- ``arch``: the operating system architecture (for instance the Linux - kernel can run on i386, sparc, and so on) - -Here's an example installation file : - -:: - - - - - The IzPack core files. - - - - - - - - - - - - - - - - - The IzPack documentation (HTML and - PDF). - - - - - -The Native Element ```` -'''''''''''''''''''''''''''''''''''''''''''''''''' - -Use this if you want to use a feature that requires a native library. The -native libraries are placed under ``bin/native/..``. There are 2 kinds of -native libraries : the iZPACK libraries and the third-party ones. The IzPack -libraries are located at ``bin/native/izpack``, you can place your own -libraries at `` bin/native/3rdparty``. It is possible to place a native -library also into the uninstaller. It is useable from CustomActions. -If one or more are referenced for it, the needed support classes are -automatically placed into the uninstaller. To place it only on operating -systems for which they are build, it is possible to define an OS restriction. -This restriction will only be performed for the uninstaller. The markup takes -the following attributes : - -- ``type`` : ``izpack`` or ``3rdparty`` -- ``name`` : the library filename -- ``stage``: stage where to use the library (install|uninstall|both) - - -```` - make a library OS-dependent -'''''''''''''''''''''''''''''''''''''''''''''''''' - -The ```` tag can be used to restrict the inclusion into the uninstaller -to a specific operating system family, architecture or version. The inclusion -into the installer will be always done. - -Here's a sample : - -:: - - - - -The Jar Merging Element ```` -'''''''''''''''''''''''''''''''''''''''''''''''''' - -If you adapt iZPACK for your own needs, you might need to merge the content -of another jar file into the jar installer. For instance, this could be a -library that you need to merge. The ```` markup allows you to merge the -raw content of another jar file into the installer and the uninstaller. It is -necessary that the paths in the jars are unique because only the contained -files of the jar are added to the installer jar, not the jar file self. The -attributes are: - -- ``src`` : the path at compile time -- ``stage``: stage where to use the contents of the additional jar file - (install|uninstall|both) - -A sample : - -:: - - - -XInclude-style constructs -------------------------- - -The xinclude element is used to include xml or text documents in your configuration files. - -The xinclude element can be used anywhere in pretty much any of the xml files used by IzPack. It is based on the XInclude recomendation produced by the W3C (http://www.w3.org/TR/xinclude/) and should be able to be used as decribed in that document. Note that as namespaces are not supported in IzPack the elements specified by the w3c have been prefixed with 'x' so 'xsi:include' becomes 'xinclude' and 'xsi:fallback' becomes 'xfallback'. - -The xinclude element has the following attributes: - -href - The location of the file to include. If this is a relative path (e.g. href='../bob.xml') then the file is resolved relative to the document that includes the xinclude element. The href element can be a remote url (e.g. href='http://example.com/file.txt') but this is not recommended. The href attribute can also be ommitted however as xpointers are not currently supported this has no meaning. - -parse - Indicates that the included file should be treated as xml, forcing the included file to be parsed (which results in all xinclude elements in the included file to also be included), or as text which includes the specified file as a text node. It can have a value of 'xml' or 'text' and defaults to 'xml' if ommitted - -xpointer - This element is not supported - -encoding - This is used when the parse attribute is 'text' to specify the character encoding of the included text document. It has no effect if parse is 'xml' - -accept - Used if the href attribute specifies a url accessible via HTTP. The value of this attribute will be added as the accpet header on the HTTP request. - - -The xfallback element -'''''''''''''''''''''' - -The xfallback element is used to provide a fallback if the xinclude element fails. It can be empty or can contain a CDATA section containing valid xml (no document fragments allowed). If it is empty then a failure to include the specified document is supressed. If it contains a CDATA section then a failure to include the specified document causes the xml specified in the CDATA is parsed (evaluating nested xinclude elements) and inserted into the document in its place. - - -For example the following use of xinclude - -:: - - - - - - hello]]> - - - - -will result in - -:: - - - hello]]> - - -if the file 'does-not-exist.xml' does indeed not exist. - - -The xfragment element -'''''''''''''''''''''' - -The xfragment element allows document fragments (xml documents without a single top level element) to be included. Simply use the xfragment as the top level element in the included document. It will be removed when the document is included. - -e.g. If I want to use xinclude to include a file containing the following fragments: - -:: - - - hello - - - there - - -I could use the xfragment element to enable it - -:: - - - - - hello - - - there - - - + + +The IzPack Elements +------------------- + +*When writing your installer XML files, it's a good idea to have a look at +the iZPACK installation DTD*. + + + + +The Root Element ```` +'''''''''''''''''''''''''''''''''''' + +The root element of an installation is ````. It takes one +required attribute : ``version``. The attribute defines the version of the +XML file layout and is used by the compiler to identify if it is compatible +with the XML file. This should be set to **1.0** for the moment. + + +The Information Element ```` +''''''''''''''''''''''''''''''''''' + +This element is used to specify some general information for the installer. +It contains the following elements : + +- ```` : the application name +- ```` : the application version +- ```` : the subpath for the default of the installation + path. A variable substitution and a maskable slash-backslash conversion + will be done. If this tag is not defined, the application name will be + used instead. +- ```` : the application official website url +- ```` : specifies the author(s) of the application. It must + contain at least one ```` element whose attributes are : + + - ``name`` : the author's name + - ``email`` : the author's email + +- ```` : specifies whether to create an uninstaller after + installation, and which name to use for it. This tag has the ``write`` + attribute, with default value `` yes``. If this tag is not specified, the + uninstaller will still be written. The ``name`` attribute can be used to + change the default name of the generated uninstaller, *i.e.* `` + uninstaller.jar``. +- ```` : specifies the minimum version of Java required to + install your program. Values can be ``1.2``, ``1.2.2``, ``1.4``, etc. The + test is a lexical comparison against the ``java.version`` System property + on the install machine. +- ````: (yes or no) specifies wether a JDK is required for the software + to be installed and executed. If not, then the user will be informed and given the + option to still proceed with the installation process or not. +- ```` : Causes a ''web installer'' to be created, and + specifies the URL packages are retrieved from at install time. The + content of the tag must be a properly formed URL. +- ```` : specifies the path for the logfile of the + `SummaryLoggerInstallerListener`. +- ```` : (yes or no) specifies if the file .installinformation should + be written which includes the information about installed packs. The default if not specified is yes. + +Here is an example of a typical ```` section : + + +:: + + + Super extractor + 2.1 beta 6 + myCompany/SExtractor + http://www.superextractor.com/ + + + + + 1.2 + + +The Packaging Element ```` +'''''''''''''''''''''''''''''''''''''' + +This element allows to specify packaging options. If not specified, the default will be to create an all in one +installer. This element will usually be used to create an installer which spans over multiple volumes, +e.g. the output will be two CDs. The packaging-element contains the following elements: + +- ```` : specifies options used by the packager. The packager tag has the ``class`` attribute, + which specifys the class to use for packaging. Currently two implementations + are available (com.izforge.izpack.compiler.Packager, com.izforge.izpack.compiler.MultiVolumePackager). + The packager-element can contain the ```` element which can have different attributes for the different + implementations of packagers. For the MultiVolumePackager, it can have the following attributes: + + - ``volumesize``: the size of the volumes + - ``firstvolumefreespace``: free space on the first volume used for the installer jar and additional resources like + readme-files etc. + + +- ```` : specifies which unpacker class should be used. Currently there are two unpacker implementations + (com.izforge.izpack.compiler.UnPacker, com.izforge.izpack.compiler.MultiVolumeUnPacker). + +Here's an example how to specify an installer which will create multiple volumes. In this example the volumes shall be +CDs with 650 megabytes. There will be an additional free space of 150 megabytes on the first volume. This will result in +the creation of an installer.jar and multiple installer.pak* files. The installer.jar plus installer.pak plus the additional +resources have to be copied on the first volume, each installer.pak. on several volumes. + +:: + + + + + + + + + +The Variables Element ```` +'''''''''''''''''''''''''''''''''''''' + +This element allows you to define variables for the variables substitution +system. Some variables are built-in, such as ``$INSTALL_PATH`` (which is the +installation path chosen by the user). When you define a set of variables, +you just have to place as many ```` tags in the file as needed. If +you define a variable named ``VERSION`` you need to type $VERSION in the +files to parse. The variable substitutor will then replace it with the +correct value. One ```` tag take the following attributes : + +- ``name`` : the variable name +- ``value`` : the variable value + +Here's a sample ```` section : + + +:: + + + + + + + +Here's a precise sample on how to use desktopshortcutcheckboxenabled and +InstallerFrame.logfilePath variables: + + +:: + + + + + + + + + + +The dynamic Variables Element ```` +'''''''''''''''''''''''''''''''''''''''''''''''''''' + +This element allows you to define dynamic variables for the variables substitution +system. In contrast to the static ```` tags +in the file as needed. Normally you would use the condition attribute to specify, when +a certain value will be set. + +One ```` tag take the following attributes : + +- ``name`` : the variable name +- ``value`` : the variable value +- ``condition`` : a condition for this variable, which has to be true to set the value + +Here's a sample ```` section : + + +:: + + + + + + + + +The Conditions Element ```` +'''''''''''''''''''''''''''''''''''''''' + +This element allows you to define conditions which can be used to dynamically change the installer, +e.g. the panels shown, the variables set, files parsed, files +executed and much more. When you define a condition it will get a type and an id. The id has to be unique. Conditions can be referenced +based on this id (e.g. with the ``RefCondition``). + +There are several built-in types of conditions. At the time of writing this, Izpack has the following built-in types: + +- ``VariableCondition``: a condition based on the value of a certain variable +- ``PackSelectionCondition``: a condition based on a pack selected for installation +- ``JavaCondition``: a condition based on a static java field or method. + +There are also boolean types to combine more than one condition: + +- ``AndCondition``: both conditions have to be true +- ``OrCondition``: only one of both conditions has to be true +- ``XOrCondition``: one condition has to be true, the other one has to be false +- ``NotCondition``: the condition has to be false + +When you define a set of conditions, you just have to write as many ```` tags as you like. A +condition can take the following attributes: + +- ``type``: the type of the condition. For built-in types, this is the lowercase portion of the condition class + name without condition appended (variable,packselection,java, ...). Custom condition types should be + referenced by the full qualified class name, e.g. de.dr.rules.MyCoolCondition. +- ``id``: the id of the condition. This will be used to refer to this conditions in other elements + +The condition element can have several child elements depending on the type of this conditions. E.g. the VariableCondition +has a name and value child element to specify, which variable should have a certain value to fullfil this condition. + +This is an example which defines four conditions, two VariableConditions, a JavaCondition and a AndCondition which will +refer to two of the first conditions. + +:: + + + + setup.type + standard + + + setup.type + expert + + + + com.izforge.izpack.util.OsVersion + IS_WINDOWS + + true + + + + + + + +Note, from IzPack 3.11 on normally, you don't have to define the compound conditions because you can use a simple +expression language. The language has the following operators: + +- ``+``: an operator for the Andcondition +- ``|``: an operator for the OrCondition +- ``\``: an operator for the XOrCondition +- ``!``: an operator for the NotCondition + +Neverthless if you define really complex conditions it's much easier to define them using the xml structure. + +More types of conditions can be defined by inheriting com.izforge.izpack.Condition class. + + +The GUI Preferences Element ```` +''''''''''''''''''''''''''''''''''''''''''' + +This element allows you to set the behavior of your installer GUI. This +information will not have any effect on the command-line installers that will +be available in future versions of iZPACK . The arguments to specify are : + +- ``resizable`` : takes ``yes`` or ``no`` and indicates whether the + window size can be changed or not. +- ``width`` : sets the initial window width +- ``height`` : sets the initial window height. + +Here's a sample : + +:: + + + + +Starting from IzPack 3.6, the look and feel can be specified in this section +on a per-OS basis. For instance you can use the native look and feels on +Win32 and OS X but use a third-party one on Unix-like platforms. To do that, +you have to add some children to the ``guiprefs`` tag: + +- ``laf``: the tag that specifies a look and feel. It has a ``name`` + parameter that defines the look and feel name. +- Each ``laf`` element needs at least one ``os`` tag, specified like in + the other parts of the specification that support this tag. +- Like you can add ``os`` elements, you can add any number of ``param`` + elements to customize a look and feel. A ``param`` elements has two + attribues: ``name`` and `` value``. + +The available look and feels are: + +- Kunststoff: ``kunststoff`` +- Liquid: ``liquid`` +- Metouia: ``metouia`` +- JGoodies Looks: ``looks`` +- Substance: ``substance`` + +If you don't specify a look and feel for a particular operating system, then +the default native one will be used: Windows on Windows, Aqua on Mac OS X and +Metal on the Unix-like variants. + + +The *Liquid Look and Feel* supports the following parameters: + +- ``decorate.frames``: ``yes`` means that it will render the frames in + Liquid style +- ``decorate.dialogs``: ``yes`` means that it will render the dialogs + in Liquid style + +The *JGoodies Looks* look and feel can be specified by using the ``variant`` +parameters. The values can be one of: + +- ``windows``: use the Windows look +- ``plastic``: use the basic Plastic look +- ``plastic3D``: use the Plastic 3D look +- ``plasticXP``: use the Plastic XP look (default). + +Here is a small sample: + +:: + + + + + + + + + + + + +The *Substance* look and feel *toned-down* themes can be specified using the +``variant`` parameter, with the value being one of: ``business, business- +blue, business-black, creme, sahara, moderate, officesilver``. We have +reduced the choice to the toned-down themes since they are the only ones to +actually look decent (the other families colors are way too saturated). +Please consult https://substance.dev.java.net/docs/skins/toneddown.html +for a gallery of the different toned-down themes. + +Starting from IzPack 3.7, some characteristics can be customized with the +```` tag. There is a separate description in the `Advanced +Features` chapter paragraph `Modifying the GUI`. + + + +The Localization Element ```` +'''''''''''''''''''''''''''''''''''''' + +This element is used to specify the language packs (langpacks) that you want +to use for your installer. You must set one ```` markup per +language. This markup takes the `` iso3`` parameter which specifies the iso3 +language code. + + +Here's a sample : + + +:: + + + + + + + + +The supported ISO3 codes are : + +========= ============================ +ISO3 code Language +========= ============================ +cat Catalunyan +chn Chinese +cze Czech +dan Danish +glg Galician +deu German +eng English +fin Finnish +fra French +hun Hungarian +ita Italian +jpn Japanese +mys Malaysian +ned Nederlands +nor Norwegian +pol Polnish +por Portuguese (Brazilian) +rom Romanian +rus Russian +scg Serbian +spa Spanish +svk Slovakian +swe Swedish +ukr Ukrainian +========= ============================ + + + +The Resources Element ```` +'''''''''''''''''''''''''''''''''''''' + +Several panels, such as the license panel and the shortcut panel, require +additional data to perform their task. This data is supplied in the form of +resources. This section describes how to specify them. Take a look at each +panel description to see if it might need any resources. Currently, no checks +are made to ensure resources needed by any panel have been included. The `` +`` element is not required, and no ```` elements are required +within. +The ```` element is the only element besides the ```` +element that is taken into consideration in referenced pack-files (see +````` element`_ for more info) + + +You have to set one ```` markup for each resource. Here are the +attributes to specify : + +- ``src`` : the path to the resource file which can be named freely of + course (for instance ``my-picture.jpg``). +- ``id`` : the resource id, depending on the needs of a particular + panel +- ``parse`` : takes ``yes`` or ``no`` (default is ``no``) - used to + specify whether the resource must be parsed at the installer compilation + time. For instance you could set the application version in a readme file + used by ``InfoPanel``. +- ``type`` : specifies the parse type. This makes sense only for a text + resource - the default is ``plain``, other values are ``javaprop, xml`` + (Java properties file and XML files) +- ``encoding`` : specifies the resource encoding if the receiver needs + to know. This makes sense only for a text resource. + +Here's a sample : + +:: + + + + + + + +The Panels Element ```` +''''''''''''''''''''''''''''''''' + +Here you tell the compiler which panels you want to use. They will appear in +the installer in the order in which they are listed in your XML installation +file. Take a look at the different panels in order to find the ones you need. +The ```` markup takes the following attributes: + +- ``classname``: which is the classname of the panel. +- ``id``: an identifier for a panel which can be used e.g. for referencing in userinput panel definitions. +- ``condition``: an id of a condition which has to be fullfilled to show this panel + + +Here's a sample : + +:: + + + + + + + + + + + +The Packs Element ```` +''''''''''''''''''''''''''''''' + +This is a crucial section as it is used to specify the files that need to be +installed. The ```` section consists of several ```` and +```` tags. + +The ```` takes the following attributes : + +- ``name``: the pack name +- ``required``: takes ``yes`` or ``no`` and specifies whether the pack + is optional or not. +- ``os``: optional attribute that lets you make the pack targeted to a + specific *operating system*, for instance ``unix``, ``mac`` and so on. +- ``preselected``: optional attribute that lets you choose whether the + pack is by default selected for installation or not. Possible values are + ``yes`` and ``no``. A pack which is not preselected needs to be + explicitly selected by the user during installation to get installed. +- ``loose``: can be used so that the files are not located in the + installer Jar. The possible values are ``true`` or ``false``, the default + beeing ``false``. The author of this feature needed to put his + application on a CD so that the users could run it directly from this + media. However, he also wanted to offer them the possibility to install + the software localy. Enabling this feature will make IzPack take the + files on disk instead of from the installer. *Please make sure that your + relative files paths are correct !* +- ``id``: this attribute is used to give a unique id to the pack to be + used for internationalization. +- ``packImgId``: this attribute is used to reference a unique resource + that represents the pack's image for the ImgPacksPanel. The resource + should be defined in the ```` element of the installation XML + using the same value for the ``id`` attribute of the ```` element. +- ``condition``: an id of a condition which has to be fullfilled to install this + package. + +The ```` takes only one attribute ``file``, which contains the +relative path (from the installation compiler) to an externally defined +packs-definition. This external packs definition is a regular IzPack +installation XML. However the only elements that are used from that XML file +are the ```` and the ```` elements. This enables a model in +which a single developer is responsible for maintaining the packs and +resources related to the development-package assigned to him. The main +install XML references these xml-files to avoid synchronization efforts +between the central installation XML and the developer-maintained installer +XMLs. + +Internationalization of the PacksPanel +''''''''''''''''''''''''''''''''''''''' + +In order to provide internationalization for the PacksPanel, so that your +users can be presented with a different name and description for each +language you support, you have to create a file named ``packsLang.xml_xyz`` +where ``xyz`` is the ISO3 code of the language in lowercase. Please be aware +that case is significant. This file has to be inserted in the resources +section of `` install.xml`` with the ``id`` and ``src`` attributes set at the +name of the file. The format of these files is identical with the +distribution langpack files located at `` +$IZPACK_HOME/bin/langpacks/installer``. For the name of the panel you just +use the pack ``id`` as the txt ``id``. For the description you use the pack +``id`` suffixed with ``.description``. + +The following sections describe the tags available for a ```` section. + + +```` - pack description +''''''''''''''''''''''''''''''''''''' + +The contents of the ```` tag describe the pack contents. This +description is displayed if the user highlights the pack during installation. + + +```` - pack dependencies +'''''''''''''''''''''''''''''''''' + +This can be used to make this pack selectable only to be installed only if +some other is selected to be installed. The pack can depend on more than one +by specifying more than one `` `` elements. +Circular depedencies are not supported and the compiler reports an error if +one occurs. + +This tag takes the following attribute: + +- ``packname``: The name of the pack that it depends on + + +```` - OS restrictions +''''''''''''''''''''''''''' + +It is possible to restrict a panel to a certain list of operating systems. +This tag takes the following attributes: + +- ``family``: unix, windows or mac +- ``name``: the exact OS name (ie Windows, Linux, ...) +- ``version``: the exact OS version (see the JVM ``os.version`` + property) +- ``arch``: the machine architecture (see the JVM ``os.arch`` + property). + + +```` +'''''''''''''''''' + +This feature can update an already installed package, therefore removing +superfluous files after installation. Here's how this feature author (Tino +Schwarze) described it on the IzPack development mailing-list: + +> Each pack can now specify an ```` tag. It supports a subset of +ant fileset syntax, e.g.: + +:: + + + + `` : will include ``lib`` and the + subdirectories of ``lib`` +- ```` : will exclude any file in any + directory starting from the base path ending by ``.java`` +- ```` : will include all the files ending + by ``.jar`` in ``lib`` +- ```` : will exclude any file in any + subdirectory starting from ``lib`` whose name contains ``FOO``. + +There area set of definitions that are excluded by default file-sets, just as +in Ant. IzPack defaults to the Ant list of default excludes. There is +currently no equivalent to the task. Default excludes are: + +:: + + **/*\~{} + **/\#*\# + **/.\#* + **/%*% + **/.\_* + **/CVS + **/CVS/** + **/.cvsignore + **/SCCS + **/SCCS/** + **/vssver.scc + **/.svn + **/.svn/** + **/.DS\_Store + + +A ```` tag can also be specified for customizing. + + +```` - parse a file after installation +'''''''''''''''''''''''''''''''''''''''''''''''''' + +Files specified by ```` are parsed after installation and may have +variables substituted. + +- ``targetfile`` : the file to parse, could be something like + ``$INSTALL_PATH/bin/launch-script.sh`` + A slash will be changed to the system dependant path separator (e.g. to a + backslash on Windows) only if no backslash masks the slash. +- ``type`` : specifies the type (same as for the resources) - the + default is ``plain`` +- ``encoding`` : specifies the file encoding +- ``os``: specifies the operating system, works like for ```` +- ``condition``: an id of a condition which has to be fullfilled to parse this file + + +```` - mark file executable or execute it +''''''''''''''''''''''''''''''''''''''''''''''''''''''' + +The ```` tag is a very useful thing if you need to execute +something during the installation process. It can also be used to set the +executable flag on Unix-like systems. Here are the attributes : + +- ``targetfile`` : the file to run, could be something like + ``$INSTALL_PATH/bin/launch-script.sh`` + Slashes are handled special (see attribute ``targetfile`` of tag + ````). +- ``class`` : If the executable is a jar file, this is the class to run + for a JavaTM program +- ``type`` : ``bin`` or ``jar`` (the default is ``bin``) +- ``stage`` : specifies when to launch : ``postinstall`` is just after + the installation is done, ``never`` will never launch it (useful to set + the +x flag on Unix). ``uninstall`` will launch the executable when the + application is uninstalled. The executable is executed before any files + are deleted. ``never`` is the default value. +- ``failure`` : specifies what to do when an error occurs : ``abort`` + will abort the installation process, ``ask`` (default) will ask the user + what to do and ``warn`` will just tell the user that something is wrong +- ``os``: specifies the operating system, works like for ```` +- ``keep`` : specifies whether the file will be kept after execution. + The default is to delete the file after is has been executed. This can be + changed by specifying ``keep="true"``. +- ``condition``: an id of a condition which has to be fullfilled to execute this file + +A ```` tag can also be specified in order to pass arguments to the +executable: + +- ````: passes the argument specified in the ``value`` attribute. + Slashes are handled special (see attribute ``targetfile`` of tag + ````. + + + +```` - make a file OS-dependent +'''''''''''''''''''''''''''''''''''''''''''''''''' + +The ```` tag can be used inside the ````, ````, +````, ````, ```` tags to restrict it's +effect to a specific operating system family, architecture or version: + +- ``family``: ``unix, windows, mac`` to specify the operating system + family +- ``name``: the operating system name +- ``version``: the operating system version +- ``arch``: the operating system architecture (for instance the Linux + kernel can run on i386, sparc, and so on) + +Here's an example installation file : + +:: + + + + + The IzPack core files. + + + + + + + + + + + + + + + + + The IzPack documentation (HTML and + PDF). + + + + + +The Native Element ```` +'''''''''''''''''''''''''''''''''''''''''''''''''' + +Use this if you want to use a feature that requires a native library. The +native libraries are placed under ``bin/native/..``. There are 2 kinds of +native libraries : the iZPACK libraries and the third-party ones. The IzPack +libraries are located at ``bin/native/izpack``, you can place your own +libraries at `` bin/native/3rdparty``. It is possible to place a native +library also into the uninstaller. It is useable from CustomActions. +If one or more are referenced for it, the needed support classes are +automatically placed into the uninstaller. To place it only on operating +systems for which they are build, it is possible to define an OS restriction. +This restriction will only be performed for the uninstaller. The markup takes +the following attributes : + +- ``type`` : ``izpack`` or ``3rdparty`` +- ``name`` : the library filename +- ``stage``: stage where to use the library (install|uninstall|both) + + +```` - make a library OS-dependent +'''''''''''''''''''''''''''''''''''''''''''''''''' + +The ```` tag can be used to restrict the inclusion into the uninstaller +to a specific operating system family, architecture or version. The inclusion +into the installer will be always done. + +Here's a sample : + +:: + + + + +The Jar Merging Element ```` +'''''''''''''''''''''''''''''''''''''''''''''''''' + +If you adapt iZPACK for your own needs, you might need to merge the content +of another jar file into the jar installer. For instance, this could be a +library that you need to merge. The ```` markup allows you to merge the +raw content of another jar file into the installer and the uninstaller. It is +necessary that the paths in the jars are unique because only the contained +files of the jar are added to the installer jar, not the jar file self. The +attributes are: + +- ``src`` : the path at compile time +- ``stage``: stage where to use the contents of the additional jar file + (install|uninstall|both) + +A sample : + +:: + + + +XInclude-style constructs +------------------------- + +The xinclude element is used to include xml or text documents in your configuration files. + +The xinclude element can be used anywhere in pretty much any of the xml files used by IzPack. It is based on the XInclude recomendation produced by the W3C (http://www.w3.org/TR/xinclude/) and should be able to be used as decribed in that document. Note that as namespaces are not supported in IzPack the elements specified by the w3c have been prefixed with 'x' so 'xsi:include' becomes 'xinclude' and 'xsi:fallback' becomes 'xfallback'. + +The xinclude element has the following attributes: + +href + The location of the file to include. If this is a relative path (e.g. href='../bob.xml') then the file is resolved relative to the document that includes the xinclude element. The href element can be a remote url (e.g. href='http://example.com/file.txt') but this is not recommended. The href attribute can also be ommitted however as xpointers are not currently supported this has no meaning. + +parse + Indicates that the included file should be treated as xml, forcing the included file to be parsed (which results in all xinclude elements in the included file to also be included), or as text which includes the specified file as a text node. It can have a value of 'xml' or 'text' and defaults to 'xml' if ommitted + +xpointer + This element is not supported + +encoding + This is used when the parse attribute is 'text' to specify the character encoding of the included text document. It has no effect if parse is 'xml' + +accept + Used if the href attribute specifies a url accessible via HTTP. The value of this attribute will be added as the accpet header on the HTTP request. + + +The xfallback element +'''''''''''''''''''''' + +The xfallback element is used to provide a fallback if the xinclude element fails. It can be empty or can contain a CDATA section containing valid xml (no document fragments allowed). If it is empty then a failure to include the specified document is supressed. If it contains a CDATA section then a failure to include the specified document causes the xml specified in the CDATA is parsed (evaluating nested xinclude elements) and inserted into the document in its place. + + +For example the following use of xinclude + +:: + + + + + + hello]]> + + + + +will result in + +:: + + + hello]]> + + +if the file 'does-not-exist.xml' does indeed not exist. + + +The xfragment element +'''''''''''''''''''''' + +The xfragment element allows document fragments (xml documents without a single top level element) to be included. Simply use the xfragment as the top level element in the included document. It will be removed when the document is included. + +e.g. If I want to use xinclude to include a file containing the following fragments: + +:: + + + hello + + + there + + +I could use the xfragment element to enable it + +:: + + + + + hello + + + there + + + .. include:: include-bottom.inc \ No newline at end of file Property changes on: src\doc-reST\installation-files.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\introduction.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\izpack-utils.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\izpack.css ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\panels.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\pdf-version.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\preamble.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\sample-install-definition.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\sample-userInputSpec.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\doc-reST\user-input.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\coi\tools\os\izpack\COIOSHelper.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\coi\tools\os\izpack\Registry.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\coi\tools\os\win\AccessControlList.java ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: src\lib\com\coi\tools\os\win\MSWinConstants.java ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: src\lib\com\coi\tools\os\win\NativeLibException.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\coi\tools\os\win\RegDataContainer.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\coi\tools\os\win\RegistryImpl.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\coi\tools\os\win\RegistryLogItem.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\coi\tools\os\win\resources\NativeLibErr.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\coi\tools\os\win\resources\NativeLibErr_de.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\ant\Property.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compiler\ByteCountingOutputStream.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compiler\DynamicVariable.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\compiler\IPackager.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\compiler\MultiVolumePackager.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\compiler\PackagerBase.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\compiler\PackagerFactory.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\compiler\PackagerHelper.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\compiler\PackInfo.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compiler\Property.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compressor\BZip2PackCompressor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compressor\DefaultPackCompressor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compressor\PackCompressor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compressor\PackCompressorBase.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compressor\PackCompressorFactory.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\compressor\RawPackCompressor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\CustomData.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\ActionBase.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\AntAction.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\AntActionInstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\AntActionUninstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\CompilerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\InstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\LateShortcutInstallListener.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\event\NativeInstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\NativeUninstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\ProgressBarInstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\RegistryInstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\RegistryUninstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\SimpleCompilerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\SimpleInstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\SimpleUninstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\SummaryLoggerInstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\event\UninstallerListener.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\gui\IzPanelConstraints.java ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\gui\IzPanelLayout.java ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\gui\LabelFactory.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\gui\LayoutConstants.java ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\ConditionHistory.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\ConditionHistoryTableCellRenderer.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\ConditionHistoryTableModel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\Debugger.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\DownloadPanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\GUIListener.java ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\InstallerException.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\installer\IUnpacker.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\LayoutHelper.java ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\LoggedInputStream.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\MultiVolumeInstaller.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\MultiVolumeUnpacker.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\UnpackerBase.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\UnpackerFactory.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\VariableHistory.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\VariableHistoryTableCellRenderer.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\VariableHistoryTableModel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\installer\WebAccessor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\installer\WebRepositoryAccessor.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\io\CorruptVolumeException.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\io\FileSpanningInputStream.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\io\FileSpanningOutputStream.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\io\VolumeNotFoundException.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\CheckedHelloPanel.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\panels\DataCheckPanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\ExtendedInstallPanel.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\panels\InstallationGroupPanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\InstallationGroupPanelAutomationHelper.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\InstallationTypePanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\JDKPathPanel.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\panels\NextMediaDialog.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\NextMediaFileFilter.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\PacksPanelBase.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\panels\PathInputPanel.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\panels\PathSelectionPanel.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\panels\ShortcutPanelAutomationHelper.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\SummaryPanel.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\panels\TextInputField.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\TreePacksPanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\TreePacksPanelAutomationHelper.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\UserPathInputPanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\UserPathPanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\UserPathPanelAutomationHelper.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\UserPathSelectionPanel.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\panels\ValidatorContainer.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\AndCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\Condition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\JavaCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\NotCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\OrCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\PackselectionCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\RefCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\RulesEngine.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\VariableCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\rules\XOrCondition.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\uninstaller\SelfModifier.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\uninstaller\UninstallerConsole.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\DebugConstants.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\ExtendedUIProgressHandler.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\IoHelper.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\JarOutputStream.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\LibraryRemover.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\Log.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\LogError.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\LogMessage.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\LogWarning.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\MonitorInputStream.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\os\RegistryDefaultHandler.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\os\RegistryHandler.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\os\unix\ShellScript.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\os\unix\UnixConstants.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\os\unix\UnixUser.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\os\unix\UnixUsers.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\os\Win_RegistryHandler.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\os\WrappedNativeLibException.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\OSClassHelper.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\PasswordEqualityValidator.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\PasswordKeystoreValidator.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\util\SpecHelper.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\SummaryProcessor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\UnixGroupProcessor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\UnixUserProcessor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\VariableSubstitutor.java ___________________________________________________________________ Name: svn:executable - * Property changes on: src\lib\com\izforge\izpack\util\xml\XMLHelper.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\com\izforge\izpack\XPackFile.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\net\n3\nanoxml\XIncludeXMLBuilder.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\lib\net\n3\nanoxml\XMLBuilderFactory.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\com\izforge\izpack\Bin_Langpacks_InstallerTest.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\com\izforge\izpack\installer\ConditionTest.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\com\izforge\izpack\TwoColumnLayoutTest.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\content-fragment.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\content.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\empty-fallback-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\empty-fallback-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\fallback-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\fallback-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-fragment-in-element-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-fragment-in-element-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-fragment-only-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-fragment-only-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-in-element-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-in-element-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-only-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-only-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-text-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-text-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-xml-as-text-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-xml-as-text-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-xml-as-xml-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\include-xml-as-xml-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\invalid-parse-attrib-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\multiple-include-expect.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\multiple-include-input.xml ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\text.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: src\tests\net\n3\nanoxml\xinclude\XIncludeXMLBuilderTestCase.java ___________________________________________________________________ Name: svn:eol-style + native Property changes on: utils\izpack2app\LICENSE.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: utils\izpack2exe\COPYING.7zS-sfx.txt ___________________________________________________________________ Name: svn:executable - * Name: svn:eol-style + native Property changes on: utils\izpack2exe\LICENSE.txt ___________________________________________________________________ Name: svn:eol-style + native Property changes on: utils\native-launcher\doc\docbook-en\manual.xml ___________________________________________________________________ Name: svn:eol-style + native