[ https://issues.jboss.org/browse/JBIDE-16401?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16401 at 2/12/14 4:32 AM: ------------------------------------------------------------------- [~mmurray] JBoss Tools never creates express.conf, it's just reading it if present. And yes, you're completely right, express.conf is created by rhc upon run for the first time. By reading it we make sure that JBoss Tools and rhc are interoperable. If it's not then we provide sane defaults within JBoss Tools (ex. we point to openshift.redhat.com as server if there's no express.conf on disk that contains such server). There are 2 locations for express.conf: * ~/.openshift/express.conf (user-settings) * /etc/openshift/express.conf (system wide settings, user-settings override the system-wide settings) As seen here: https://github.com/openshift/rhc/blob/master/man/express.conf.5#L23 you see all the settings that express.conf may contain. We currently only support: * default_rhlogin (username) * libra_server (openshift server) * libra_domain (default domain - looks deprecated for rhc). We plan to include *timeout*: OSJC-66 was (Author: adietish): [~mmurray] JBoss Tools never creates express.conf, it's just reading it if present. If it's not then we provide sane defaults within JBoss Tools (ex. we point to openshift.redhat.com as server if there's no express.conf on disk that contains such server). -- 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