[
https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi...
]
Lucia Jelinkova commented on JBIDE-10133:
-----------------------------------------
I've tried to add -Dlibra_server=AAA entry to the -vmargs section of jbdevstudio.ini,
restarted JBDS and expected the wizard to fail at some point - but it didn't and
happily created a new application.
I am also not able to find the configuration files - in case I do not have openshift
command line installed, do I need to create this file manually?
OpenShift URL should be looked up in the configuration files that the
CLI uses (so we can easily switch to staging environment)
-------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-10133
URL:
https://issues.jboss.org/browse/JBIDE-10133
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.M4
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M5
There's currently no easy way for a (power-) user to switch to the staging
environment since the PaaS URL is inidicated in the code.
--
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