[
https://issues.jboss.org/browse/JBIDE-12909?page=com.atlassian.jira.plugi...
]
Stefan Bunciak commented on JBIDE-12909:
----------------------------------------
[~adietish]: I'm not completely sure, so please correct me if I'm doing something
wrong.
I've created a new OpenShift application in JBDS 6.0.0.CR1, then opened the same
workspace with JBDS 6.0.0.Beta1b, and although I was able to publish the application,
server editor seems not to have the connection set correctly: !connection.png|thumbnail!
As a result, these context menu items, available from the Server adapter, doesn't
work:
* Show in - Web Browser (nothing happens)
* OpenShift - Tail Files (Please verify that the associated OpenShift Application still
exists.)
* OpenShift - Environment variables
* OpenShift - Port Forwarding...
Otherwise, please provide steps to verify this issue. Thank you!
existing connections are not loaded in Beta1
---------------------------------------------
Key: JBIDE-12909
URL:
https://issues.jboss.org/browse/JBIDE-12909
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.0.0.CR1
In JBIDE-12826 we described how we'd stay compatible to old username based settings
for project- and connection settings. The project settings are handled correctly but
existing connections are not loaded as described:
{quote}
connection list (connection pool, that's also used by the OpenShift Explorer):
* The current key/values only use the username. Migration:
* we keep the existing preference key/values
* we create a new preference key
* the connection pool is loading the old and new preferences
* the connection pool is storing the connections that define connections to the default
server to the old preferences
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira