[ https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10133: ---------------------------------------- #1: we should support -Dlibra_server= #2: read from ~/.openshift/express.conf -- 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

[ https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10133: ------------------------------------- Summary: OpenShift URL should be looked up in the configuration files that the CLI uses (so we can easily switch to staging environment) (was: OpenShift URL should be looked up in a properties file (so we can easily switch to staging environment)) -- 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

[ https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10133 at 12/16/11 3:30 AM: -------------------------------------------------------------------- no, it's up to the user to make sure he/she provides valid urls, the wizard will not fall back if the url given is not valid. it will only fall back if there's no setting at all). The hierarchy of the possible configurations is as follows (the first one superseeding the 2nd etc.): 1) system properties (may be set by providing "-Dlibra_server=..." to the jvm when starting it. 2) user configuration (<user-home-dir>/.openshift/express.conf) 3) system-wide configuration (/etc/openshift/express.conf) 4) default configuration (not changeable by the user, default hard coded in the java client library) was (Author: adietish): no, it's up to the user to make sure he/she provides valid urls, the wizard will not fall back to a valid one. The hierarchy of the possible configurations is as follows (the first one superseeding the 2nd etc.): 1) system properties (may be set by providing "-Dlibra_server=..." to the jvm when starting it. 2) user configuration (<user-home-dir>/.openshift/express.conf) 3) system-wide configuration (/etc/openshift/express.conf) 4) default configuration (not changeable by the user, default hard coded in the java client library) -- 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

[ https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10133: ------------------------------------------ I'll reproduce the -Dlibra_server usecase to see why this actually fails. Since you cannot spot the config files, and the wizard still worked, it fell back to the built in default which uses openshift.redhat.com as libra_server. I'm not completely sure by heart at which point the openshift CLI commands create those files. But to me there's little use to create those by hand. Why not just installing the CLI tools and do some manipulations until you get the files? The CLI tools would also allow you to verify what the wizard tells you (domain name, applications etc.) -- 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

[ https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10133 at 12/16/11 12:44 PM: --------------------------------------------------------------------- @Lucia: I just tried here with a fresh eclipse that I installed JBoss Tools to and added a -Dlibra_server= to my eclipse.ini: {code} -vmargs -Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=256m -Xms40m -Xmx1024m -Dlibra_server=invalidhonkabonka.com {code} The OpenShift wizard failed when trying to validate my credentials, immediately returned "invalid credentials". So I can't reproduce your finding about the -Dlibra_server. Please double check your setup. was (Author: adietish): @Lucia: I just tried here with a fresh eclipse that I installed JBoss Tools to and added the following to eclipse.ini: {code} -vmargs -Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=256m -Xms40m -Xmx1024m -Dlibra_server=humpadumpa.com {code} The OpenShift wizard failed when trying to validate my credentials, immediately returned "invalid credentials". So I can't reproduce your finding about the -Dlibra_server. Please double check your setup. -- 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

[ https://issues.jboss.org/browse/JBIDE-10133?page=com.atlassian.jira.plugi... ] Lucia Jelinkova resolved JBIDE-10133. ------------------------------------- Resolution: Done -- 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