[JBoss JIRA] (JBDS-4303) Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos)
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4303?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4303.
-----------------------------
Verified in build 188.
> Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos)
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4303
> URL: https://issues.jboss.org/browse/JBDS-4303
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Fix For: 10.4.0.AM2
>
>
> Current implementation shows errors and warning under item selected for installation.
> See confirmation page error message for virtualbox Installer [here|https://github.com/redhat-developer-tooling/developer-platform-insta...].
> Confirmation page controller should run Virtualization detection along with installed components detection and show warning under virtualbox item if it is detected or selected for install.
> If Virtualization firmware status cannot be detected (windows 7) message should say:
> * Make sure hardware virtualization is enabled on your platform if supported to improve performance.
> if Hardware Virtualization is Disabled:
> * Please enable hardware virtualization for your platform to improve performance
> If Hardware Virtualization is Enabled, no message is required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4343) Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*'
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4343?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4343:
--------------------------------
Fix Version/s: 11.0.0.GA
> Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*'
> -------------------------------------------------------------------------
>
> Key: JBDS-4343
> URL: https://issues.jboss.org/browse/JBDS-4343
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.4.0.AM2
> Environment: devstudio-10.4.0.AM2-v20170330-1543-B348-installer-standalone.jar
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
> Attachments: install.png
>
>
> The installer spends several minutes in this state:
> !install.png|thumbnail!
> Just for comparison
> - AM1 installation takes total of about 2 minutes 15 seconds
> - AM2 takes 5 minutes 40 seconds
> There is no shortage of memory or disk I/O availability, the CPU is not topped off (even though AM2 eats up more CPU itself during this time).
> DTRACE=true reveals nothing interesting really, this is what it says in the particular moment (notice how much time the operation takes):
> {noformat}
> Configuring toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64
> Preparing to commit the provisioning operation.
> Committing the provisioning operation.
> Operation completed in 289855 ms.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3730:
--------------------------------
Fix Version/s: 11.0.0.GA
(was: 10.4.0.AM2)
> 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: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 11.0.0.GA
>
>
> 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
(v7.2.3#72005)
9 years