[JBoss JIRA] (JBIDE-22367) Create and use Neon.RC3/4 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22367?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22367:
-------------------------------
Description:
Prepare TP to use Neon.0.RC3 or RC4 bits, which will be available June 3 0r 10. Cloned from JBIDE-22200.
https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S...
Story points: 21 (fibonacci)
* jbt tp,
* jbds tp,
* central tp;
* jbt-build-sites,
* jbds site build;
* update install/matrix jobs to use new Eclipse JEE/platform binary;
* mailing list announcements
was:
Prepare TP to use Neon M6 or M7 bits, which will be available 03/18 to 03/25 or 04/29 to 05/06. Cloned from JBIDE-21386.
https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S...
Story points: 21 (fibonacci)
* jbt tp,
* jbds tp,
* central tp;
* jbt-build-sites,
* jbds site build;
* update install/matrix jobs to use new Eclipse JEE/platform binary;
* mailing list announcements
> Create and use Neon.RC3/4 target platform
> -----------------------------------------
>
> Key: JBIDE-22367
> URL: https://issues.jboss.org/browse/JBIDE-22367
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.4.0.Alpha3
>
>
> Prepare TP to use Neon.0.RC3 or RC4 bits, which will be available June 3 0r 10. Cloned from JBIDE-22200.
> https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S...
> Story points: 21 (fibonacci)
> * jbt tp,
> * jbds tp,
> * central tp;
> * jbt-build-sites,
> * jbds site build;
> * update install/matrix jobs to use new Eclipse JEE/platform binary;
> * mailing list announcements
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-21823:
-------------------------------------
Resolution: (was: Done)
Assignee: Jeff Cantrill (was: Jeff MAURY)
> Unable to re-edit Service config
> --------------------------------
>
> Key: JBIDE-21823
> URL: https://issues.jboss.org/browse/JBIDE-21823
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.4.0.Alpha2
>
>
> Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes.
> Steps to reproduce:
> - select a service in the OpenShift Explorer
> - click on the {{Edit...}} command.
> - in the JSON editor for the service config, note the resource version. Eg:
> {code}
> {
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38301",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> },
> ...
> {code}
> - make some changes and save
> - the service config version should have incremented:
> {code}
> {
> "kind" : "Service",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38390",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> }
> ....
> {code}
> - close the config editor
> - re-open the config editor
> *ASSERT: the editor displays the latest config*
> *FAIL the editor displays the initial config*
> *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version*
> {code}
> Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
> Could not update resource jee-sample: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "jee-sample",
> "kind": "services"
> },
> "code": 409
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months