December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4029) Fix Account validation messages so they don't move UI elements when appears/disappears

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4029?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4029: -------------------------------- Sprint: (was: devex #124 December 2017) > Fix Account validation messages so they don't move UI elements when appears/disappears > -------------------------------------------------------------------------------------- > > Key: JBDS-4029 > URL: https://issues.jboss.org/browse/JBDS-4029 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > Fix For: 10.3.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[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: -------------------------------- Sprint: (was: devex #124 December 2017) > 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.3.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 (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[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: (was: devex #124 December 2017) > 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.3.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 (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3824) Installer: it is not clear what will be downloaded on Confirmation page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3824?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3824: -------------------------------- Sprint: (was: devex #124 December 2017) > Installer: it is not clear what will be downloaded on Confirmation page > ----------------------------------------------------------------------- > > Key: JBDS-3824 > URL: https://issues.jboss.org/browse/JBDS-3824 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Labels: ui > Fix For: 10.3.0.AM2 > > > While on the _Confirmation_ page inside installer, there is a button _Download & Install_. User already downloaded 1.5G installer and it's not clear what will be downloaded in the next step. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3869: -------------------------------- Sprint: (was: devex #124 December 2017) > platform installer should check/warn if Hyper-V is already enabled. > ------------------------------------------------------------------- > > Key: JBDS-3869 > URL: https://issues.jboss.org/browse/JBDS-3869 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 10 Pro, 64 bit. > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 10.3.0.AM2 > > > The platform installer should check and warn if Hyper-V is already enabled on Windows systems. > Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4066) DevSuite Installer Account step styles are inconsistent with Target Folder step

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4066?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4066: -------------------------------- Sprint: (was: devex #124 December 2017) > DevSuite Installer Account step styles are inconsistent with Target Folder step > ------------------------------------------------------------------------------- > > Key: JBDS-4066 > URL: https://issues.jboss.org/browse/JBDS-4066 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > Fix For: 10.3.0.AM2 > > Attachments: screenshot-1.png, screenshot-2.png > > > Account page looks different from Target Location page: > 1. Fields with invalid values have red glow border with gradient; > 2. There are three areas to show error messages one for each field and one for login error; > 3. Username and password error have styling different from login error and from validation messages on Target Location page; > 4. Field height is different from Target Location field; > 5. When validation messages appear they move elements on Account Page back and forth; > Account Step: > !screenshot-1.png! > Target Location Step: > !screenshot-2.png!: -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4223) Promisify installer's detection methods

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4223?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4223: -------------------------------- Sprint: (was: devex #124 December 2017) > Promisify installer's detection methods > --------------------------------------- > > Key: JBDS-4223 > URL: https://issues.jboss.org/browse/JBDS-4223 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.3.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.AM2 > > > Current implementation gets callbak to notify about detection results, method should return promise instance instead to simplify chaining and testing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4208) Detection for installed components always counts cygwin as detected on macOS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4208?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4208: -------------------------------- Sprint: (was: devex #124 December 2017) > Detection for installed components always counts cygwin as detected on macOS > ---------------------------------------------------------------------------- > > Key: JBDS-4208 > URL: https://issues.jboss.org/browse/JBDS-4208 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Environment: macOS > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.AM2 > > > It means confirmation page message about detected components always increase number of detected components by one. If only Java is detected it would say "We found 2 installed components" one is Java and another one is Cygwin which is not visible under macOS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4159: ------------------------------------- That is correct. > On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-4159 > URL: https://issues.jboss.org/browse/JBDS-4159 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 1.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.3.0.GA > > > On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases. > here is the error: > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > There was an error while executing `VBoxManage`, a CLI used by Vagrant > for controlling VirtualBox. The command and stderr is shown below. > Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"] > Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) > VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-4159 at 12/20/16 12:06 AM: ---------------------------------------------------------------- [~aileenc] this should be fixed with next CDK release, approximately within next 6 weeks. For Windows 10 Pro Hyper-V would be selected by default if enabled for other windows platforms virtualbox will stay as a requirement. VM image is going to be the same for virtualbox and Hyper-V setup and bundled installer is going to be roughly the same size as it is right now. was (Author: dgolovin): [~aileenc] this should be fixed with next CDK release, approximately within next 6 weeks. For Windows 10 Pro Hyper-V would be selected by default if enabled for other windows platforms virtualbox will stay as a requirement. VM image is going to be the same for virtualbox and Hyper-V setup and bundled installer is not going to be roughly the same size as it is right now. > On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-4159 > URL: https://issues.jboss.org/browse/JBDS-4159 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 1.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.3.0.GA > > > On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases. > here is the error: > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > There was an error while executing `VBoxManage`, a CLI used by Vagrant > for controlling VirtualBox. The command and stderr is shown below. > Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"] > Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) > VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

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 December 2016