[jbosstools-issues] [JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK
[
https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-23626:
---------------------------------------
I recall a comment recently where I thought I heard the intent is for the origin api to be
backwards compatible for the foreseeable future. It might be better to direct intended
compatibility questions to the aos-devel mailing list. In regards to which oc version is
not compatible with which server version, can you please provide more specifics about what
doesn't work? My recollection, we rely on oc for: port forwarding, logs, syncing
code. Logs I know for certain can be moved away from oc dependency and I don't
remember doing that.
Preferences: link to download oc may lead me to try to use an
incompatible oc binary for my origin/CDK
------------------------------------------------------------------------------------------------------
Key: JBIDE-23626
URL: https://issues.jboss.org/browse/JBIDE-23626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.2.AM3
Reporter: Andre Dietisheim
Labels: oc_binary, preferences
Fix For: 4.4.3.AM1
oc 1.4, which is available from github is not compatible with the lastest CDK 2.3
(it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries
which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know
what oc he should use.
Our preferences offer a link to the github releases but there's no info nor logic
that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc
1.2 with CDK 2.3 etc.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)