[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3865?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3865:
--------------------------------
Sprint: (was: devex #118 July 2016)
> Platform installer should warn about known bad versions of Vagrant.
> -------------------------------------------------------------------
>
> Key: JBDS-3865
> URL: https://issues.jboss.org/browse/JBDS-3865
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> Vagrant 1.8.1 installed
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.1.0.GA
>
>
> The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list.
> Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3798) Repeated component detection keeps stale values
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3798:
--------------------------------
Sprint: (was: devex #118 July 2016)
> Repeated component detection keeps stale values
> -----------------------------------------------
>
> Key: JBDS-3798
> URL: https://issues.jboss.org/browse/JBDS-3798
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160413-107
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.GA
>
> Attachments: screenshot-1.png
>
>
> Installer detects existing tools on confirmation page. If after that a change happens (like the user uninstalls VirtualBox) and then the user goes to the previous page and to confirm page again - the change is correctly detected, but instead of replacing the old option, there are now both options for 'install' and 'use existing'. Plus the count of detected components stays the same.
> Using the existing (no longer existing in fact) installation fails, naturally.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3822:
-------------------------------------
This error is replicated when installer does not produce any changes in windows registry related to new product installation. It means if virtualbox, vagrant or openjdk installed message does not appear, because any of this installation creates record in windows products and features list. This issue should be fixed when installer registers uninstaller in windows registry.
> Disable the annoying "This program might not have installed correctly" on cancelation
> -------------------------------------------------------------------------------------
>
> Key: JBDS-3822
> URL: https://issues.jboss.org/browse/JBDS-3822
> 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.1.0.GA
>
> Attachments: devsuite.manifest
>
>
> Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it.
> This should be avoided by providing an application manifest that indicates support for certain Windows versions.
> Docs here:
> https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3731) Installer - Failure to install a component does not halt the installer's progress bar
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3731?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3731:
--------------------------------
Sprint: (was: devex #118 July 2016)
> Installer - Failure to install a component does not halt the installer's progress bar
> -------------------------------------------------------------------------------------
>
> Key: JBDS-3731
> URL: https://issues.jboss.org/browse/JBDS-3731
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Windows10
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.GA
>
> Attachments: Screenshot (20).png, Screenshot (24).png
>
>
> See the attached screenshots - when the bug described in JBDS-3722 was encountered, the virtualbox installation status bar continued to proceed, even though the installation of the affected component had stopped. This will be confusing to the user.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
Sprint: (was: devex #118 July 2016)
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.GA
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months