Description of problem: In a recent discussion around https://issues.jboss.org/browse/JBIDE-19852 (which deals with jar installers while adding a runtime in JBoss Tools / JBoss Developer Studio), it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. Details are here: http://docs.codehaus.org/display/IZPACK/Unattended+Installations The idea is that you could run this: java -DINSTALL_PATH=/default/path -jar installer.jar And this would pre-fill the installation path to the path given in the command. I tried this with jboss-dv-installer-6.1.0.redhat-3.jar , but the installation path prefilled during the installation was still set to /Users/rasp/DV-6.1.0/jboss-eap-6.3 . Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Run the installer like this: java -DINSTALL_PATH=/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 -jar jboss-dv-installer-6.1.0.redhat-3.jar Actual results: This path is prefilled: /Users/rasp/DV-6.1.0/jboss-eap-6.3 Expected results: During the installation, this path will be prefilled as the installation path: /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 Additional info: If this gets implemented, it will help us with the tooling - the Eclipse tooling allows to download zip or jar archives of a product (depending on what's available). in the case of a zip, we will ask the user where to extract it and it's easy. In the case of an installer jar, it would be good if we could start the installer from within the tooling with the path already prefilled.
Hi Martin, Are there any other useful variables / properties you'd like to be able to specify in this way? Thanks, Tom
TargetPanel method loadDefaultDirFromVariables now checks for the INSTALL_PATH system property, if it exists it uses its value for the default install path. Therefore you can now set the default install path through the command line. java -DINSTALL_PATH=(path) -jar... Thanks, Emmett
The property is not working for automatic installer. If it serves to override install path of the installer shouldn't it work for the automatic as well? In my view it would be best to maintain consistency between the three types.
-DINSTALL_PATH can now be used to specify a new install path for the automated installation (instead of the one chosen during the installation in which the auto.xml file was generated). Thanks, Emmett Undherhill
Radim Hopp <rhopp> updated the status of jira JBIDE-19852 to Closed