[JBoss JIRA] (JBDS-3757) Add some logging to setup routines
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3757:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Add some logging to setup routines
> ----------------------------------
>
> Key: JBDS-3757
> URL: https://issues.jboss.org/browse/JBDS-3757
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM2
>
>
> We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3758:
--------------------------------
Labels: ui (was: )
> when something goes wrong, give user call to action / report of what went wrong
> -------------------------------------------------------------------------------
>
> Key: JBDS-3758
> URL: https://issues.jboss.org/browse/JBDS-3758
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Labels: ui
> Fix For: 10.2.0.AM2
>
> Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png
>
>
> I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS.
> I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached).
> If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ?
> Also, should there be a call to action for the user?
> Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3766:
-------------------------------------
As a solution for this issue we probably should require restart fro user machine if something was installed before to make sure all system environment changes are current.
> 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: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-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.2.0.AM2
>
> 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)
9 years, 6 months
[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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3766:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> 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: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-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.2.0.AM2
>
> 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)
9 years, 6 months
[JBoss JIRA] (JBDS-3779) Consider changing the installation order
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3779?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3779:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Consider changing the installation order
> ----------------------------------------
>
> Key: JBDS-3779
> URL: https://issues.jboss.org/browse/JBDS-3779
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM2
>
>
> Right now there are the following installation 'streams':
> 1. JDK -> JBDS - looks fine to me
> 2. Virtualbox -> Cygwin -> Vagrant -> CDK - this is the one I have an issue with.
> The second stream starts with Virtualbox which first needs to be downloaded. Maybe some other component could do something productive while Virtualbox is downloading so it might save some time. In other words - could something other than a download start the installation?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months