[
https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich edited comment on JBIDE-21920 at 3/21/16 10:09 AM:
-------------------------------------------------------------------------
We set in preferences property
{code}
IOpenShiftCoreConstants.OPENSHIFT_CLI_LOC = "openshift.cli.location"
{code}
Is it not renamed into 'openshift.restclient.oc.location'?
No, wrong guess, in restclient it is IBinaryCapability.OPENSHIFT_BINARY_LOCATION which is
set to the value of IOpenShiftCoreConstants.OPENSHIFT_CLI_LOC in RSync.
was (Author: scabanovich):
We set in preferences property
{code}
IOpenShiftCoreConstants.OPENSHIFT_CLI_LOC = "openshift.cli.location"
{code}
Is it not renamed into 'openshift.restclient.oc.location'?
Cannot use features which are using oc binary
---------------------------------------------
Key: JBIDE-21920
URL:
https://issues.jboss.org/browse/JBIDE-21920
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Priority: Blocker
Labels: openshift_v3
Fix For: 4.3.1.CR1
After latest update of nightly JBT I am not able to get logs from pods(/builds) or work
with server adapter, because there is something wrong with setting oc path. When I set
path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g.
getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property
openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)