[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 #123 November 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.GA
>
>
> 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, 4 months
[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 #123 November 2016)
> 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.2.0.GA
>
> 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, 4 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: (was: devex #123 November 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.GA
>
> 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
(v7.2.3#72005)
9 years, 4 months
[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:
--------------------------------
Sprint: (was: devex #123 November 2016)
> 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.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
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4121) Run DevSuite Installer with Elevated privileges on Mac OSX
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4121?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4121:
--------------------------------
Sprint: (was: devex #123 November 2016)
> Run DevSuite Installer with Elevated privileges on Mac OSX
> ----------------------------------------------------------
>
> Key: JBDS-4121
> URL: https://issues.jboss.org/browse/JBDS-4121
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Environment: Mac OS X
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: DevSuite.zip
>
>
> During installation PATH environment variable should be updated. For example to make permanent changes for PATH variable /etc/paths file should be modified and that requires administrative privileges.
> For Alpha release we could be running installer with sudo
> {code}sudo open DevSuite.app{code}
> Another option to investigate is using AppleScript and run the same shell script above with elevated privileges like this
> {code}do shell script «open DevSuite.app» with administrator privileges{code}
> that would trigger standard UI Dialog requesting user login/password with administrative privileges. This should be included int DevSuite.app package configuration after it is assembled by electron packages.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 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: (was: devex #123 November 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.GA
>
>
> 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
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4087) Mark as invalid Vagrant versions known to be not working
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4087?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4087:
--------------------------------
Sprint: (was: devex #123 November 2016)
> Mark as invalid Vagrant versions known to be not working
> --------------------------------------------------------
>
> Key: JBDS-4087
> URL: https://issues.jboss.org/browse/JBDS-4087
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.2.0.GA
>
>
> Vagrant version superior to 1.8.4 are known to be non-working, please mark them as invalid during installation of the components isntead of saying that there is a newer version.
> For my part there was no clue on what was the issue, i was based on the latest at the moment 1.8.6.
> When using JBDS, I had a timeout when trying to launch the Container in Server view and the console starting the server was displaying no errors
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 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:
--------------------------------
Sprint: (was: devex #123 November 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.GA
>
>
> 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, 4 months