August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3635: -------------------------------- Story Points: 13 > Add the ability to detect/select existing dependencies/tools > ------------------------------------------------------------ > > Key: JBDS-3635 > URL: https://issues.jboss.org/browse/JBDS-3635 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Critical > Labels: havoc, ui > Fix For: 10.1.0.GA > > Attachments: pdkinstaller.png, Technologies 5.pdf > > > Generic rules for detection and validation are: > 1. We do our best to detect what is installed on user's machine: vagrant, virtualbox, java and do not detect cdk, cygwin, or DevStudio; > 2. When version is detected it must be verified against the range of what we believe valid versions; it might be defined as a set or condition. > vagrant: minimal and tested version is 1.7.4, all newer releases are good to continue with warning except 1.8.0 which is known to have networking problems; > virtualbox: minimal and tested 5.0.8 and all newer releases are good to continue with warning; > jvm: minimal and tested is 1.8 and all newer releases are good to continue with warning; > 3. For vagrant and virtual box if detected version is out of the range, installer shows error message with explanation and doesn't let go any further until detected version is uninstalled, which should be done manually and then installer should be restarted; If nothing is detected included versions can be installed or installer could be configured to use specific location; > 4. For JVM if not supported version is detected, included one can be used or installer could be pointed to right location to use. > 5. When location for required software set manually installer try will try detect version and verify it using (2); > 6. When version cannot be detected and manually selected location looks like required install, installer should let to proceed with warning. > It would be great if the installer allowed the user to use some of the required tools they have already installed. > The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. > The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): > !pdkinstaller.png|thumbnail! > [~dgolovin] & [~crobson], what's your opinion on this? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3633) Uninstaller does nothing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3633?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3633: -------------------------------- Story Points: 8 > Uninstaller does nothing > ------------------------ > > Key: JBDS-3633 > URL: https://issues.jboss.org/browse/JBDS-3633 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.GA > > > Current implementation just removes record about installation from windows registry. > What it should do: > 1. Remove virtual box from vagrant: > {code}vagrant box remove cdkv2{code} > 2. Remove virtual machine from virtual box > {code}vboxmanage --unregister ${vmname}{code} > 3. Uninstall what was installed: > vargant > virtual box > developer studio > 4. Delete: > CDK > Open JDK 8 > 5. Cleanup PATH env variable -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3841: -------------------------------- Story Points: 13 > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Critical > Labels: user-docs > Fix For: 10.1.0.GA > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3732) Installer - A summary of what was installed should be displayed after a successful install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3732?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3732: -------------------------------- Story Points: 13 > Installer - A summary of what was installed should be displayed after a successful install > ------------------------------------------------------------------------------------------ > > Key: JBDS-3732 > URL: https://issues.jboss.org/browse/JBDS-3732 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.1.0.GA > > Attachments: Add_an_inventory.png > > > See the attached screenshot - it would be helpful/informative to the user to see a summary/inventory of the components that were installed or updated during a successful install. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3708) Installer - All-in-one installer could/should be made self-documenting

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3708?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3708: -------------------------------- Story Points: 21 > Installer - All-in-one installer could/should be made self-documenting > ---------------------------------------------------------------------- > > Key: JBDS-3708 > URL: https://issues.jboss.org/browse/JBDS-3708 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.GA > > > It would be helpful to users if they could press a 'help' button to view a more verbose version of this document: > https://issues.jboss.org/secure/attachment/12399497/installer%20flow.pdf > Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3719) Initial search for an existing JBDS is present but disabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3719?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3719: -------------------------------- Story Points: 5 > Initial search for an existing JBDS is present but disabled > ----------------------------------------------------------- > > Key: JBDS-3719 > URL: https://issues.jboss.org/browse/JBDS-3719 > 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.1.0.GA > > > The installer calls the functionality to search for an existing JBDS when the confirm page loads, but the method has a built-in check that just interrupts it. Meaning - checking an existing installation will only proceed if a folder was selected by the user, the initial search will not. > Is this by design? If it is there is no point in initiating the search automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3837) Installer UI does not communicate errors to the user properly

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3837?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3837: -------------------------------- Story Points: 21 > Installer UI does not communicate errors to the user properly > ------------------------------------------------------------- > > Key: JBDS-3837 > URL: https://issues.jboss.org/browse/JBDS-3837 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.GA > > Attachments: screen-installer2.png > > > The installation has failed with no reason given. Please see screenshot attached. > We need to improve the UI too - If something fails the progress bar should be changed to red color etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3990) Create mock server to test online installer with public links before they are available

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3990?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3990: -------------------------------- Story Points: 8 > Create mock server to test online installer with public links before they are available > --------------------------------------------------------------------------------------- > > Key: JBDS-3990 > URL: https://issues.jboss.org/browse/JBDS-3990 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > This server should let to test download from public links before they are available. Server should use local settings to map requests to locally downloaded resources. developers.redhat.com should be mapped to localhost through hosts file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

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: -------------------------------- Story Points: 8 > 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.1.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 (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3832) Investigate if one can find if a pre-installed virtualbox also contains network drivers

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3832?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3832: -------------------------------- Story Points: 21 > Investigate if one can find if a pre-installed virtualbox also contains network drivers > --------------------------------------------------------------------------------------- > > Key: JBDS-3832 > URL: https://issues.jboss.org/browse/JBDS-3832 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.GA > > > In order to start CDK we need Virtualbox with its networking support installed. Since the vbox installer allows the users to only install the bare VM, we should find a way to tell if the vbox network drivers have been installed in the detected installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016