April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3749) With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3749?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3749: ------------------------------------ Assignee: Nick Boldt > With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install > --------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3749 > URL: https://issues.jboss.org/browse/JBDS-3749 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.GA > > Attachments: vb-not-detected-can-not-proceed.png, vbox5016-installed-detected-cant-selected-i-want-to-use-existing-vb.png, win10-details.png > > > Downloaded Setup-bundled-0.0.2-20160331-23.exe > Logged in using my RHD credentials > On the Confirmation step of the installer, I see an unchecked box for ORACLE VIRTUALBOX v5 and an unchecked box for "I want to use the existing VirtualBox". > I can't check either of them (when I cursor over them I see a red NOT circle) so as a result the "Download & Install" button is greyed out - it too has a red NOT circle when I cursor over it. > I have VB installed here: > C:\Program Files\Oracle\VirtualBox\VirtualBox.exe > Version 5.0.16 r105871 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3749) With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3749?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3749: ------------------------------------ Assignee: Denis Golovin (was: Nick Boldt) > With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install > --------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3749 > URL: https://issues.jboss.org/browse/JBDS-3749 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.GA > > Attachments: vb-not-detected-can-not-proceed.png, vbox5016-installed-detected-cant-selected-i-want-to-use-existing-vb.png, win10-details.png > > > Downloaded Setup-bundled-0.0.2-20160331-23.exe > Logged in using my RHD credentials > On the Confirmation step of the installer, I see an unchecked box for ORACLE VIRTUALBOX v5 and an unchecked box for "I want to use the existing VirtualBox". > I can't check either of them (when I cursor over them I see a red NOT circle) so as a result the "Download & Install" button is greyed out - it too has a red NOT circle when I cursor over it. > I have VB installed here: > C:\Program Files\Oracle\VirtualBox\VirtualBox.exe > Version 5.0.16 r105871 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3764) Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3764?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3764: ------------------------------- Priority: Blocker (was: Major) > Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3764 > URL: https://issues.jboss.org/browse/JBDS-3764 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Attachments: JDK_detection.png > > > See attached screenshot. > To recreate this issue: > * Install using installer: Setup-bundled-0.0.2-20160401-33, accept all defaults > * Attempt to install "over" the installation just completed by running the installer a 2nd time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3644) Document installer/cdk/devstudio basic workflow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3644?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3644: ------------------------------------ Assignee: Misha Ali > Document installer/cdk/devstudio basic workflow > ----------------------------------------------- > > Key: JBDS-3644 > URL: https://issues.jboss.org/browse/JBDS-3644 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, installer > Reporter: Max Rydahl Andersen > Assignee: Misha Ali > Priority: Blocker > Fix For: 9.1.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3765) Installer - Component Detection - Fails to recognize VirtualBox 5.0.8

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3765?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3765: ------------------------------- Priority: Blocker (was: Major) > Installer - Component Detection - Fails to recognize VirtualBox 5.0.8 > --------------------------------------------------------------------- > > Key: JBDS-3765 > URL: https://issues.jboss.org/browse/JBDS-3765 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > > See attached screenshot. > Steps to recreate: > * Install VirtualBox 5.0.8, add c:\Hashicorp\Vagrant\bin to the PATH > * Attempt to install using installer Setup-bundled-0.0.2-20160401-33, select to not install a new VirtualBox -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3766: ------------------------------- Priority: Blocker (was: Major) > Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log? > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3766 > URL: https://issues.jboss.org/browse/JBDS-3766 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Attachments: install.log, Is_Restart_Needed.png, vagrant.log, vbox.log > > > See attached log files. > After some install attempts, Vagrant fails to start. The vagrant install log reports the following: > {code} > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2. > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time. > {code} > Is a system restart needed to ensure that the vagrant installation is successful on Windows? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3766: ------------------------------- Labels: havoc (was: ) > Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log? > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3766 > URL: https://issues.jboss.org/browse/JBDS-3766 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Attachments: install.log, Is_Restart_Needed.png, vagrant.log, vbox.log > > > See attached log files. > After some install attempts, Vagrant fails to start. The vagrant install log reports the following: > {code} > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2. > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time. > {code} > Is a system restart needed to ensure that the vagrant installation is successful on Windows? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3750) Include Virtual Box 5.0.16 (instead of 5.0.8) in the bundled installer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3750?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3750: --------------------------------- Priority: Critical (was: Major) > Include Virtual Box 5.0.16 (instead of 5.0.8) in the bundled installer > ---------------------------------------------------------------------- > > Key: JBDS-3750 > URL: https://issues.jboss.org/browse/JBDS-3750 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.1.0.GA > > > Latest version of VB available [1] is 5.0.16. > We should update the installer to include the latest, rather than 5.0.8. > [1] https://www.virtualbox.org/wiki/Downloads -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3631: --------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.GA) > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc, ui > Fix For: 10.0.0.Alpha1 > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3635: --------------------------------- Priority: Critical (was: Major) > Add the ability to detect/select existing dependencies/tools > ------------------------------------------------------------ > > Key: JBDS-3635 > URL: https://issues.jboss.org/browse/JBDS-3635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Critical > Labels: havoc, ui > Fix For: 9.1.0.GA > > Attachments: pdkinstaller.png, Technologies 5.pdf > > > Generic rules for detection and validation are: > 1. We do our best to detect what is installed on user's machine: vagrant, virtualbox, java and do not detect cdk, cygwin, or DevStudio; > 2. When version is detected it must be verified against the range of what we believe valid versions; it might be defined as a set or condition. > vagrant: minimal and tested version is 1.7.4, all newer releases are good to continue with warning except 1.8.0 which is known to have networking problems; > virtualbox: minimal and tested 5.0.8 and all newer releases are good to continue with warning; > jvm: minimal and tested is 1.8 and all newer releases are good to continue with warning; > 3. For vagrant and virtual box if detected version is out of the range, installer shows error message with explanation and doesn't let go any further until detected version is uninstalled, which should be done manually and then installer should be restarted; If nothing is detected included versions can be installed or installer could be configured to use specific location; > 4. For JVM if not supported version is detected, included one can be used or installer could be pointed to right location to use. > 5. When location for required software set manually installer try will try detect version and verify it using (2); > 6. When version cannot be detected and manually selected location looks like required install, installer should let to proceed with warning. > It would be great if the installer allowed the user to use some of the required tools they have already installed. > The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. > The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): > !pdkinstaller.png|thumbnail! > [~dgolovin] & [~crobson], what's your opinion on this? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016