[
https://issues.jboss.org/browse/JBIDE-12798?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12798:
-------------------------------------
Labels: new_and_noteworthy (was: )
Release Notes Text: Before Beta1 there was no way to define a server for the Eclipse
Tooling only. OpenShift for JBoss Tools was always refererring to the server that was
defined in the rhc configurations: ~/.openshift/express.con and
/etc/openshift/express.conf. In Beta1 we now allow the user to define a custom server with
every new connection. The user may choose to use the default server, that's defined in
the express.conf. But he can also define whatever host runs the OpenShift instance he
wants to deal with:
openshift.redhat.com, a local liveCD, an instance within is LAN etc.
When logging into OpenShift, allow to use existing connections or
create a new one
----------------------------------------------------------------------------------
Key: JBIDE-12798
URL:
https://issues.jboss.org/browse/JBIDE-12798
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Affects Versions: 4.0.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: new_and_noteworthy
Fix For: 4.0.0.Beta1
Attachments: 2012-10-04 14.34.bmml, 2012-10-04 14.34.bmml, 2012-10-04 14.34.png,
connection-dialog-existing.png, connection-dialog-new.png
We're currently using username + password to connect to an OpenShift server. In
JBIDE-12572 we now added a server-url to be able to connect to different user (without
changing the express.conf files).
We should now add the ability to name connections. When you would look at / edit the
connections you would now furthermore supply a name (JBIDE-12572). When launching the
application wizard you would then choose the connection (by its name).
--
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