-
Bug
-
Resolution: Done
-
Major
-
4.1.0.Alpha2
-
None
-
- EXEC: Set (both) trace options for OpenShift client to true
- EXEC: Start JBDS with -debug option
- EXEC: Do some communication with OpenShift (create connection, etc.) to see the debug output in eclipse log / trace log
- EXEC: Set (both) trace options for OpenShift client to false
- EXEC: Start JBDS without -debug option
- RESULT: The debug output is still being produced:
The same for eclipse .log and trace.log in workspace/.metadata
EXEC: Set (both) trace options for OpenShift client to true EXEC: Start JBDS with -debug option EXEC: Do some communication with OpenShift (create connection, etc.) to see the debug output in eclipse log / trace log EXEC: Set (both) trace options for OpenShift client to false EXEC: Start JBDS without -debug option RESULT: The debug output is still being produced: The same for eclipse .log and trace.log in workspace/.metadata
eclipse.buildId=unknown
java.version=1.6.0_29
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.jbds.product.product
Command-line arguments: -os linux -ws gtk -arch x86 -product com.jboss.jbds.product.product
Info
Fri Apr 12 11:09:48 CEST 2013
Requesting GET on https://openshift.redhat.com/broker/rest/domains/pipistik (RestService.java:138)
