March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-573) Prepare test for Data Transformation on Fuse on EAP

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-573?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík reassigned JBTIS-573: ---------------------------------- Assignee: Tomáš Sedmík (was: Andrej Podhradsky) > Prepare test for Data Transformation on Fuse on EAP > --------------------------------------------------- > > Key: JBTIS-573 > URL: https://issues.jboss.org/browse/JBTIS-573 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > > SSIA > + see https://issues.jboss.org/browse/ENTESB-4618 - example is attached -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21831: ------------------------------------- I see, yes you are right. I can change the default. > Change host to localhost when cdk is selected in new server dialog > ------------------------------------------------------------------ > > Key: JBIDE-21831 > URL: https://issues.jboss.org/browse/JBIDE-21831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: new-cdk-server.png > > > When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter. > This was spotted and brought up by [~mlabuda]. > For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3678) Installer - On startup, username field is not automatically selected

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3678?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3678: ----------------------------- > Installer - On startup, username field is not automatically selected > -------------------------------------------------------------------- > > Key: JBDS-3678 > URL: https://issues.jboss.org/browse/JBDS-3678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 9.1.0.CR1 > > > Small usability point - when a user starts up the installer, the username field is not automatically selected. If the user simply starts typing, the characters types are ignored. The user must manually select the username field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3678) Installer - On startup, username field is not automatically selected

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3678?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3678: -------------------------------- > Installer - On startup, username field is not automatically selected > -------------------------------------------------------------------- > > Key: JBDS-3678 > URL: https://issues.jboss.org/browse/JBDS-3678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 9.1.0.CR1 > > > Small usability point - when a user starts up the installer, the username field is not automatically selected. If the user simply starts typing, the characters types are ignored. The user must manually select the username field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3678) Installer - On startup, username field is not automatically selected

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3678?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3678: -------------------------------- > Installer - On startup, username field is not automatically selected > -------------------------------------------------------------------- > > Key: JBDS-3678 > URL: https://issues.jboss.org/browse/JBDS-3678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 9.1.0.CR1 > > > Small usability point - when a user starts up the installer, the username field is not automatically selected. If the user simply starts typing, the characters types are ignored. The user must manually select the username field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3678) Installer - On startup, username field is not automatically selected

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3678?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3678. --------------------------------- Resolution: Done > Installer - On startup, username field is not automatically selected > -------------------------------------------------------------------- > > Key: JBDS-3678 > URL: https://issues.jboss.org/browse/JBDS-3678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 9.1.0.CR1 > > > Small usability point - when a user starts up the installer, the username field is not automatically selected. If the user simply starts typing, the characters types are ignored. The user must manually select the username field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3678) Installer - On startup, username field is not automatically selected

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3678?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3678: ----------------------------------- Assignee: Denis Golovin > Installer - On startup, username field is not automatically selected > -------------------------------------------------------------------- > > Key: JBDS-3678 > URL: https://issues.jboss.org/browse/JBDS-3678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 9.1.0.CR1 > > > Small usability point - when a user starts up the installer, the username field is not automatically selected. If the user simply starts typing, the characters types are ignored. The user must manually select the username field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21815: ---------------------------------------- Sprint: devex #3 February 2016, devex #4 March 2016 (was: devex #3 February 2016) > Image metadata not refreshed after name change > ---------------------------------------------- > > Key: JBIDE-21815 > URL: https://issues.jboss.org/browse/JBIDE-21815 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1 > > > Steps to reproduce: > - open the *Deploy Docker Image* wizard > - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}} > - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again. > - ASSERT: the metadata should have been updated > - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21823: ---------------------------------------- Sprint: devex #3 February 2016, devex #4 March 2016 (was: devex #3 February 2016) > 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 > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1 > > > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21828: ---------------------------------------- Sprint: devex #3 February 2016, devex #4 March 2016 (was: devex #3 February 2016) > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016