Jan Richter created JBDS-3730: --------------------------------- Summary: Headless standalone installer can be run with xml config that contains eap bundle Key: JBDS-3730 URL: https://issues.jboss.org/browse/JBDS-3730 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Reporter: Jan Richter Assignee: Denis Golovin Priority: Minor One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following: {noformat}[ Starting automated installation ] [INFO] Selected JVM Information [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64 [INFO] Vendor : Oracle Corporation [INFO] Version : 1.8.0_72 [INFO] Arch : 64-bit [ Starting to unpack ] [ Processing package: P2 Director Application (1/4) ] [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ] [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ] [ Processing package: JBoss Enterprise Application Platform (4/4) ] [ WARNING: Error executing /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] [ ERROR: The installation was not completed ] [ Unpacking finished ] com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source) at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) at com.izforge.izpack.installer.Installer.main(Unknown Source) [ Automated installation FAILED! ]{noformat} The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)