[JBoss JIRA] (JBDS-3834) Install fail - what next?
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3834:
------------------------------------
Assignee: Denis Golovin
> Install fail - what next?
> -------------------------
>
> Key: JBDS-3834
> URL: https://issues.jboss.org/browse/JBDS-3834
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.0.0.Alpha1
>
> Attachments: 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
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22187) Duplicate Openshift connections
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-22187:
----------------------------------
Summary: Duplicate Openshift connections
Key: JBIDE-22187
URL: https://issues.jboss.org/browse/JBIDE-22187
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Jeff MAURY
It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TOOLSDOC-714) JBDS 9.1 GA: Win Installation - changing JDK with installed JBDS fails
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-714?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-714:
------------------------------------
It looks like this is now resolved and does not require any docs. [~ldimaggio], correct me if I'm wrong here. Till then, I'm setting this to resolved.
> JBDS 9.1 GA: Win Installation - changing JDK with installed JBDS fails
> ----------------------------------------------------------------------
>
> Key: TOOLSDOC-714
> URL: https://issues.jboss.org/browse/TOOLSDOC-714
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Misha Ali
> Labels: Windows
>
> Ideally, if the user has an existing JBDS installation in their Program Files folder in Win and the installer is used to install the JDK, the installation fails when the installer tries to alter the jbdevstudio.ini file to point to the new JDK. Windows does not allow a protected folder's contents to be modified without admin rights. The issue is being discussed and may require documentation.
> Source: https://issues.jboss.org/browse/JBDS-3695
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years