[
https://issues.jboss.org/browse/JBIDE-12320?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12320:
------------------------------------------
There's an interesting guide to evolve REST APIs in OpenStack. It states what's
acceptable for them and what's not:
http://wiki.openstack.org/APIChangeGuidelines
In general terms only additions are acceptable. Removals or semantical changes are
not.Generally speaking I'd pretend that the very same should apply to what we should
be able to expect from OpenShift.
On the other hand
https://bugzilla.redhat.com/show_bug.cgi?id=838611 shows that semanitcal
changes can happen and I guess that we'll never be at 100% safe from these. Relying on
graceful evolution of our client side classes wont be possible I guess.
support protocol version 1.1 in openshift-java-client
-----------------------------------------------------
Key: JBIDE-12320
URL:
https://issues.jboss.org/browse/JBIDE-12320
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.0.0.Alpha1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: new_and_noteworthy
Fix For: 4.0.0.Alpha1
the REST protocol that we use to talk to the OpenShift broker was bumped to 1.1 today.
The change that triggers it is a change in the cartridges that you get reported when
listing them on a application. We have to support protocol 1.1 for the
openshift-java-client
--
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