[
https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-23626:
------------------------------------------
back when this issue was created, [~rob.stryker] and [~mlabuda] we're reporting that
oc 1.4 wasnt working with CDK 2.3. Can you both please chime in and confirm?
But there's also another topic in this issue: in v2 the enterprise and free versions
would differ quite substantially. The free version would progress continously while the
enterprise version would only progress in bigger steps, eventually backporting fixes. If
this proves to be the case for OpenShift v3 (which I believe is the goal as it is for all
our products, ex. Wildfly vs EAP, Fedora vs RHEL etc)., then we have to use the enterprise
version of oc for an enterprise version of OpenShift. But I fear that we dont have such
information at hand currently. I dont even know who to ask for such information.
[~jcantrill] do you know?
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)