September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3614) DevSuite Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3614?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3614: -------------------------------- Fix Version/s: 10.2.0.AM2 (was: 10.2.0.AM1) > DevSuite Installer > ------------------ > > Key: JBDS-3614 > URL: https://issues.jboss.org/browse/JBDS-3614 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.2.0.AM2 > > > Make installer that has: > VirtualBox > Vagrant > Cygwin > CDK > (custom VagrantFile?) > (docker client?) > OpenJDK > Red Hat Developer Studio 9.1 > (with or without JBoss EAP ? - EAP 7 not available) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

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.2.0.AM2 (was: 10.2.0.AM1) > 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.2.0.AM2 > > Attachments: installing.png, install_error.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 (v6.4.11#64026)

9 years, 6 months

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: -------------------------------- Labels: ui (was: havoc ui) > 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.2.0.AM2 > > Attachments: installing.png, install_error.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 (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3628) Cache downloaded files to reuse them in case of installation failure

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3628?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3628: -------------------------------- Fix Version/s: 10.2.0.AM2 (was: 10.2.0.AM1) > Cache downloaded files to reuse them in case of installation failure > -------------------------------------------------------------------- > > Key: JBDS-3628 > URL: https://issues.jboss.org/browse/JBDS-3628 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Labels: havoc > Fix For: 10.2.0.AM2 > > > This would be time saver for testing and in case of error during installation. Instead of downloading the same files over and over again installer would continue to download only missing ones. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

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.2.0.AM2 (was: 10.2.0.AM1) > 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.2.0.AM2 > > > 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 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3631: -------------------------------- Fix Version/s: 10.2.0.AM2 (was: 10.2.0.AM1) > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, ui > Fix For: 10.2.0.AM2 > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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: -------------------------------- Fix Version/s: 10.2.0.AM2 (was: 10.2.0.AM1) > 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.2.0.AM2 > > > 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, 6 months

1
0
0 / 0

[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: -------------------------------- Fix Version/s: 10.2.0.AM2 (was: 10.2.0.AM1) > 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.2.0.AM2 > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3642: -------------------------------- Fix Version/s: 10.2.0.AM2 (was: 10.2.0.AM1) > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 10.2.0.AM2 > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3642: -------------------------------- Labels: ui (was: havoc) > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: ui > Fix For: 10.2.0.AM2 > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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