[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:
--------------------------------
Sprint: devex #121 October 2016
> 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, 5 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: devex #121 October 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.2.0.AM2
>
> 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, 5 months
[JBoss JIRA] (JBDS-3701) Add check for an existing Java to find if it is JRE or JDK
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3701?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3701:
--------------------------------
Sprint: devex #121 October 2016
> Add check for an existing Java to find if it is JRE or JDK
> ----------------------------------------------------------
>
> Key: JBDS-3701
> URL: https://issues.jboss.org/browse/JBDS-3701
> 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: ui
> Fix For: 10.2.0.AM2
>
>
> JBDS will run on both, but in order to develop something the user needs a JDK. The detection/selection will allow using JRE distribution of Java without even a warning. We should find out what kind of Java the user has selected and at least display a warning if it is not JDK (or just not allow JRE).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 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: devex #121 October 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: ui
> Fix For: 10.2.0.AM2
>
> 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, 5 months
[JBoss JIRA] (JBDS-4058) Installer does not validate VAGRANT_HOME when used
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4058?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4058:
--------------------------------
Fix Version/s: 10.2.0.AM2
Story Points: 3
Sprint: devex #121 October 2016
> Installer does not validate VAGRANT_HOME when used
> --------------------------------------------------
>
> Key: JBDS-4058
> URL: https://issues.jboss.org/browse/JBDS-4058
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
>
> As per JBDS-3838, we require users with space in their name to use VAGRANT_HOME environment variable. The problem is, the installer will let you proceed without validating the variable contents.
> Something like "x:\this definitely has no spaces\" will allow the user to proceed with installation, which inevitably fails. We need to validate if the path stored in the variable is valid, that the selected drive actually exists, and that there are no spaces.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months