[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13664 at 2/28/13 5:25 PM: ------------------------------------------------------------------- yes, it solved it, great, thanks! I did a "mvn clean install" in my plugins and pointed a vanilla Juno-SR1 to the freshly build repo (while adding the JBT nightlies updates site). Tracing for the OpenShift client then became available in the preferences: !openshift-tracing-available.png! and once the flag were set to *true*, tracing output was produced: {code} tail -f /home/adietish/workspace/.metadata/trace.log | Worker-1 | 2013-02-28 23:22:48.519 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Requesting GET on https://openshift.redhat.com/broker/rest/user | | Worker-1 | 2013-02-28 23:22:48.520 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | creating connection to https://openshift.redhat.com/broker/rest/user using username "<USERNAME>" and password "<PASSWORD>" | | Worker-1 | 2013-02-28 23:22:49.764 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Unmarshalling response {"data":{"capabilities":{"subaccounts":false,"gear_sizes":["small","medium"]},"consumed_gears":2,"links":{"LIST_KEYS":{"href":"https://openshift.redhat.com/broker/rest/user/keys","method":"GET","optional_params":[],"rel":"Get SSH keys","required_params":[]},"ADD_KEY":{"hre... new SSH key","required_params":[{"description":"Name of the key","invalid_options":[],"name":"name","type":"string","valid_options":[]},{"description":"Type of Key","invalid_options":[],"name":"type","type":"string","valid_options":["ssh-rsa","ssh-dss","ecdsa-sha2-nistp256-cert-v01@openssh.com","ecdsa-sha2-nistp384-cert-v01@openssh.com","ecdsa-sha2-nistp521-cert-v01@openssh.com","ssh-rsa-cert-v01@openssh.com","ssh-dss-cert-v01@openssh.com","ssh-rsa-cert-v00@openssh.com","ssh-dss-cert-v00@openssh.com","ecdsa-sha2-nistp256","ecdsa-sha2-nistp384","ecdsa-sha2-nistp521"]},{"description":"The key portion of an rsa key (excluding ssh-rsa and comment)","invalid_options":[],"name":"content","type":"string","valid_options":[]}]}},"login":"adietish@redhat.com","max_gears":10,"plan_id":"freeshift","usage_account_id":null},"messages":[],"status":"ok","supported_api_versions":[1.0,1.1,1.2,1.3],"type":"user","version":"1.0"} | | Worker-1 | 2013-02-28 23:22:49.774 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Requesting GET on https://openshift.redhat.com/broker/rest/domains | | Worker-1 | 2013-02-28 23:22:49.776 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | creating connection to https://openshift.redhat.com/broker/rest/domains using username "<USERNAME>" and password "<PASSWORD>" | | Worker-1 | 2013-02-28 23:22:50.987 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Unmarshalling response {"data":[{"id":"honkabonka2","links":{"GET":{"href":"https://openshift.redhat.com/broker/rest/domains/honkabonka2","method":"GET","optional_params":[],"rel":"Get domain","required_params":[]},"LIST_APPLICATIONS"... applications","required_params":[]},"ADD_APPLICATION&..., e.g: php-5.3","name":"cartridge","type":"string","valid_options":["nodejs-0.6","jbossews-2.0","zend-5.6","ruby-1.9","python-3.3","jbossas-7","python-2.6","jenkins-1.4","ruby-1.8","python-2.7","jbosseap-6.0","diy-0.1","jbossews-1.0","php-5.3","perl-5.10"]},{"default_value":false,"description":"Mark application as scalable","name":"scale","type":"boolean","valid_options":[true,false]},{"default_value":"small","description":"The size of the gear","name":"gear_profile","type":"string","valid_options":["small","medium"]}],"rel":"Create new application","required_params":[{"description":"Name of the application","invalid_options":["amentra","... domain","required_params":[{"description":"Name of the domain","invalid_options":[],"name":"id&quo... delete domain. i.e. delete any applications under this domain","name":"force","type":"boolean","valid_options":[true,false]}],"rel":"Delete domain","required_params":[]}},"suffix":"rhcloud.com"}],"messages":[],"status":"ok","supported_api_versions":[1.0,1.1,1.2,1.3],"type":"domains","version":"1.0"} {code} was (Author: adietish): yes, it solved it, great, thanks! I did a "mvn clean install" in my plugins and pointed a vanilla Juno-SR1 to the freshly build repo (while adding the JBT nightlies updates site). Tracing for the OpenShift client then became available in the preferences: !openshift-tracing-available.png! -- 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