[JBoss JIRA] (JBDS-3726) Installer - Installer fails to overwrite/move an existing JDK
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3726?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3726:
---------------------------------
Priority: Major (was: Critical)
> Installer - Installer fails to overwrite/move an existing JDK
> -------------------------------------------------------------
>
> Key: JBDS-3726
> URL: https://issues.jboss.org/browse/JBDS-3726
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Windows 10
> Build: 0.0.2-20160324-14
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: Havoc
> Fix For: 9.1.0.GA
>
>
> Attempting to overwrite a JDK that was installed by a previous installer run fails with this (permissions) error:
> Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Extract C:\Users\jbossqa\AppData\Local\Temp\7zS1C02.tmp\jdk.zip to c:\DeveloperPlatform SUCCESS
> Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Rename c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64to c:\DeveloperPlatform\jdk8
> Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk - Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8'
> Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk failed to install: Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3711) JBDS setup is called after installation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3711?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3711:
---------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> JBDS setup is called after installation
> ---------------------------------------
>
> Key: JBDS-3711
> URL: https://issues.jboss.org/browse/JBDS-3711
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
>
> What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since the JDK path is otherwise already set during the headless installation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3711) JBDS setup is called after installation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3711?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3711:
---------------------------------
Target Release: 10.0.0.GA (was: 9.1.0.GA)
> JBDS setup is called after installation
> ---------------------------------------
>
> Key: JBDS-3711
> URL: https://issues.jboss.org/browse/JBDS-3711
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since the JDK path is otherwise already set during the headless installation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3766:
--------------------------------------
[~ldimaggio] can you please attache your log or resolve this as not reproducible ;)
> 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: Critical
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
> 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
[JBoss JIRA] (JBDS-3765) Installer - Component Detection - Fails to recognize VirtualBox 5.0.8
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3765?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3765.
----------------------------------
Resolution: Done
Must be fixed by now. Please reopen if still reproducible.
> 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: Critical
> Fix For: 9.1.0.GA
>
>
> 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
[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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3766:
---------------------------------
Target Release: 10.0.0.GA (was: 9.1.0.GA)
> 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: Critical
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
> 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
[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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3766:
---------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> 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: Critical
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
> 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