[
https://issues.jboss.org/browse/JBIDE-19520?page=com.atlassian.jira.plugi...
]
Ma Deshuai edited comment on JBIDE-19520 at 3/27/15 1:37 AM:
-------------------------------------------------------------
[~adietish] I can reproduce, The steps is:
1. Open connection Wizard dialog and The default server type is v2, In the dialog there
are Username and password.
2. Select the server type to "OpenShift 3"
3. Select the server type back to "OpenShift 2"
4. The "Username" and "password" input dialog disappear
5. Input the v2 server and never connect to the v2.
Additional info:
If there is no step 2, Openshift V2 can connect successfully
was (Author: deshuai):
[~adietish] I can reproduce, The steps is:
1. Open connection Wizard dialog and The default server type is v2, In the dialog there
are Username and password.
2. Select the server type to "OpenShift 3"
3. Select the server type back to "OpenShift 2"
4. The "Username" and "password" input dialog disappear
5. Input the v2 server and never connect to the v2.
Unable to establish a connection in v2 or v3
--------------------------------------------
Key: JBIDE-19520
URL:
https://issues.jboss.org/browse/JBIDE-19520
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Reporter: Jeff Cantrill
Assignee: Andre Dietisheim
Priority: Blocker
Labels: connection_wizard
Fix For: 4.3.0.Alpha2
After installing v2 and v3 plugin, unable to establish a connection in v2 or v3.
Noticed:
* Creds are visible initially for v2 but disappear and never reappear after flipping back
and forth between v2 and v3
* Trying a v2 connection after entering a URL never connects
* Canceling the v2 connection the URL text box is repopulated with the default URL, I
suspect 'trying to connect' is not getting the URL that was entered
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)