April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4044) Use angular $http service instead of node request module

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4044?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4044: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Use angular $http service instead of node request module > -------------------------------------------------------- > > Key: JBDS-4044 > URL: https://issues.jboss.org/browse/JBDS-4044 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.4.0.GA > > > Since April $http service seems to support progress reporting for http requests: > 1. See httpspec.js in this [commit|https://github.com/angular/angular.js/commit/01b18450882da9bb9c903...]; > 2. XMLHTTPRequest documentation [here|https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Usin...]. > Questions: > 1. Does it support redirects? > 2. How authentication is supported? > Benefits: > 1. Native browser service, so probably should be working faster; > 2. Proxy settings picked up from system settings, so there is no need to set up environment variables before running the installer. > Drawbacks: > 1. Proxy errors are not detectable (?) It just printed out to console without providing info trough returning error parameter for callback; > 2. No third party multi-threaded downloaders that would support restarting download from the position where it failed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4068) There should be UI to show additional info for detected JDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4068?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4068: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > There should be UI to show additional info for detected JDK > ----------------------------------------------------------- > > Key: JBDS-4068 > URL: https://issues.jboss.org/browse/JBDS-4068 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > > When vagrant and virtualbox are provided each from the only vendor, the story is different for OpenJDK, because there are several vendors: > - Oracle; > - Red Hat; > - Zulu; > - IBM. > Also on 64-bit system both 32-bit and 64-bit JDK could be installed. > Current UI for OpenJDK component shows only version fro detected JDK. There should be UI to see additional info about selected JDK like vendor and arch. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3834) Install fail - what next?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3834: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Install fail - what next? > ------------------------- > > Key: JBDS-3834 > URL: https://issues.jboss.org/browse/JBDS-3834 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Misha Ali > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > Attachments: error.PNG, fail_install.PNG > > > Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4229: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > If updating CDK installation error reported > ------------------------------------------- > > Key: JBDS-4229 > URL: https://issues.jboss.org/browse/JBDS-4229 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Reporter: Jeff MAURY > Labels: cdk, installer > Fix For: 10.4.0.GA > > Attachments: nstall.log > > > If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3965: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Add a note on how to launch cdk in last page of devsuite installer > ------------------------------------------------------------------ > > Key: JBDS-3965 > URL: https://issues.jboss.org/browse/JBDS-3965 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > > Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk. > This is described here: JBIDE-22734 > What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon. > Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View. > So here's a proposal: > Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched? > Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.4.0.GA > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3826) Some components fail with folder name containing non-standard characters

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3826?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3826: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Some components fail with folder name containing non-standard characters > ------------------------------------------------------------------------ > > Key: JBDS-3826 > URL: https://issues.jboss.org/browse/JBDS-3826 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.4.0.GA > > > I have tried installing into this folder: > {noformat}c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform{noformat} > And JBDS installation failed immediately, the install.log was not very helpful. > {noformat}Fri, 15 Apr 2016 11:49:50 GMT-INFO: jbds - Execute c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds failed to install: Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3622) Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3622?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3622: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3622 > URL: https://issues.jboss.org/browse/JBDS-3622 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > Attachments: install_error.png, installing.png > > > See the attached screenshot - the install has failed - the only option for the user is to close the installer window. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3632) Using a pre packaged version of Cygwin that doesn't require the installer to download packages

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3632?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3632: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Using a pre packaged version of Cygwin that doesn't require the installer to download packages > ---------------------------------------------------------------------------------------------- > > Key: JBDS-3632 > URL: https://issues.jboss.org/browse/JBDS-3632 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.4.0.GA > > > It should be possible to install Cygwin, and then package that install in such a way that we can do a more silent install that doesn't require packages to be downloaded. > Some clues can be found here: https://cygwin.com/ml/cygwin/2010-03/msg00877.html > The fix should modify the bundle build to download packages into temp folder and then zip them. This zip then included into bundle installer. > {code}c:\DevelopmentSuite\cygwin\setup-x86_64.exe -D --no-admin --quiet-mode --only-site -l c:\DevelopmentSuite\cygwin\packages --site http://mirrors.xmission.com/cygwin --categories Base --packages openssh,rsync --root c:\DevelopmentSuite{code} > Another modification should be done to cygwin installer to check for included zip with packages, unpack it and do installation from local folder instead > {code}c:\DevelopmentSuite\cygwin\setup-x86_64.exe --no-admin --quiet-mode -L -l c:\DevelopmentSuite\cygwin\packages --categories Base --packages openssh,rsync --root c:\DevelopmentSuite\cygwin{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4252) Installer waits for failed Virtualbox installation (MacOS)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4252?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4252: -------------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > Installer waits for failed Virtualbox installation (MacOS) > ---------------------------------------------------------- > > Key: JBDS-4252 > URL: https://issues.jboss.org/browse/JBDS-4252 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.GA > Reporter: Andre Dietisheim > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > Attachments: waiting-for-virtualbox-install-that-failed.png > > > steps to reproduce: > # ASSERT: make sure that you have VirtualBox 5.1.x running but the app is removed from the Applications folder > # EXEC: launch installer, log in and select VirtualBox etc. > Result: > Installer fails to install VirtualBox. > !waiting-for-virtualbox-install-that-failed.png! > In the logs you see the following: > {code} > 0:233: execution error: installer: Error - The installer has detected running virtual machines. Please shut down all running VirtualBox machines and then restart the installation. (1) > {code} > The installer simply states "Failed". It would be nice if the installer could provide more details on why/what failed. Sparing me from having to inspect the logs. > It simply states "Failed" for VirtualBox, the "Red Hat Container Development Kit" process is waiting for VirtualBox to get installed even though that failed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 April 2017