[
https://issues.jboss.org/browse/JBIDE-10191?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10191:
-------------------------------------
Steps to Reproduce:
# ASSERT: have a libra server configured (libra_server='') in your configuration
files (/etc/openshift/express.conf or ~/.openshift/express.conf)
ex. libra_server='openshift.redhat.com'
# ASSERT: have a launch configuration that sets a different system property libra_server
(-Dlibra_server=)
ex. -Dlibra_server=stg.openshift.redhat.com (to be able to access the staging server,
you'd have to be on our VPN and set the proxy as described here:
https://engineering.redhat.com/trac/Libra/wiki/Staging_Environment)
# EXEC: launch an Eclipse IDE and verify to what server the wizard connects (ex. by having
different users on staging and on prod).
Result: it connects to the server that is found in the configuration files, not to the one
that is set in the system properties.
was:
# ASSERT: have a libra server configured (libra_server='') in your configuration
files (/etc/openshift/express.conf or ~/.openshift/express.conf)
ex. libra_server='openshift.redhat.com'
# ASSERT: have a launch configuration that sets a different system property libra_server
(-Dlibra_server=)
ex. -Dlibra_server=stg.openshift.redhat.com (to be able to access the staging server,
you'd have to be on our VPN and set the proxy as described here:
https://engineering.redhat.com/trac/Libra/wiki/Staging_Environment)
# EXEC: launch an Eclipse IDE and see to what server the wizard connects
Result: it connects to the server that is found in the configuration files, not to the one
that is set in the system properties.
System properties are ignored
-----------------------------
Key: JBIDE-10191
URL:
https://issues.jboss.org/browse/JBIDE-10191
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira