February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21678?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21678: ----------------------------------------------- Method ConnectionWizardPageModel.init() gets instance of IConnectionFactory and passes it to getSignupUrl(). However, in the case of new connection, the passed value is null, and connection factory is computed in initConnection(). So, the fix has to take that into account and replace {code} this.signupUrl = getSignupUrl(host, connectionFactory); {code} with {code} this.signupUrl = getSignupUrl(host, this.connectionFactory); {code} Value signupUrl is used in page by method showHideSignupLink() (the method name does not need further comments :) ). > New Connection wizard: Getting started info is not visible by default > ---------------------------------------------------------------------- > > Key: JBIDE-21678 > URL: https://issues.jboss.org/browse/JBIDE-21678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: default_new_conn.png, rendered_new_conn.png > > > In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection). > See screenshot of fresh opened New Connection wizard: > !default_new_conn.png! > and after checkbox is (un)checked or server type is changed: > !rendered_new_conn.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-71) Create Relevant Methods Completion Engine

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-71?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-71: ------------------------------- Assignee: Ian Stewart-Binks (was: Gorkem Ercan) > Create Relevant Methods Completion Engine > ----------------------------------------- > > Key: ERT-71 > URL: https://issues.jboss.org/browse/ERT-71 > Project: Eclipse Release Train > Issue Type: Sub-task > Components: JSDT > Reporter: Ian Stewart-Binks > Assignee: Ian Stewart-Binks > > If a user invokes code completion when trying to write an object's method, relevant methods of that object *that have already been used* in the current JS file should be proposed. This should be extensible enough such that relevant methods used outside of the file can be suggested in the future as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-65) Create Keyword Completion Engine

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-65?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-65: ------------------------------- Assignee: Ian Stewart-Binks (was: Gorkem Ercan) > Create Keyword Completion Engine > -------------------------------- > > Key: ERT-65 > URL: https://issues.jboss.org/browse/ERT-65 > Project: Eclipse Release Train > Issue Type: Sub-task > Components: JSDT > Reporter: Ian Stewart-Binks > Assignee: Ian Stewart-Binks > > When a user invokes code completion, a list of contextually practical keywords should be suggested. > * After a user has typed a few characters and invoked code completion, keywords prefixed by those few characters should be suggested. For instance, if the user has just typed 'del', 'delete' should be suggested. Similarly, if the user has just typed 'd', all of the keywords that start with the letter 'd' should be suggested. > * Keywords based on relevance should also be suggested. For instance, consider the case when a user has begun a *do while* block. If the user writes the *do* and the *block* and invokes code completion, *while(<CR>);* should be one of the suggestions. A similar functionality for an *if else* should be implemented, as well. > Questions: > * Should keywords that match templates be suggested even though their template counterpart is in the list of suggestions? > * Should keywords be suggested within JSDocs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-66) Create Identifier Completion Engine

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-66?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-66: ------------------------------- Assignee: Ian Stewart-Binks (was: Gorkem Ercan) > Create Identifier Completion Engine > ----------------------------------- > > Key: ERT-66 > URL: https://issues.jboss.org/browse/ERT-66 > Project: Eclipse Release Train > Issue Type: Sub-task > Components: JSDT > Reporter: Ian Stewart-Binks > Assignee: Ian Stewart-Binks > > When a user invokes code completion, a set of useful identifier should be suggested to them. These identifiers should only be identifiers that are visible within the current scope from the current file. This should first support identifiers using ES5 keywords, and be extensible enough for ES6 keywords to fit in later on. Function identifiers from the current file and scope should be included as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-24) JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-24?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-24: ------------------------------- Assignee: (was: Gorkem Ercan) > JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841] > ----------------------------------------------------------------------------------- > > Key: ERT-24 > URL: https://issues.jboss.org/browse/ERT-24 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Use org.eclipse.wst.validation.validatorV2 to allow 3rd parties to introduce new validator. > In the process the internal syntax validation should also be moved to use the same extension point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21681) Truncated lines seen on openshift login page

by Xia Zhao (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21681?page=com.atlassian.jira.plugi... ] Xia Zhao commented on JBIDE-21681: ---------------------------------- [~adietish] I intended to report issue #1 , just updated the problem description field. Sorry for the confusing, I cloned this one from an old one. My fault. Thanks, Xia > Truncated lines seen on openshift login page > -------------------------------------------- > > Key: JBIDE-21681 > URL: https://issues.jboss.org/browse/JBIDE-21681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.CR1-v20160212-1935-B177 > OS: Fedora 17 & 22 > Reporter: Xia Zhao > Priority: Minor > Labels: login_wizard, openshift_v3 > Attachments: Screenshot from 2016-02-15 10-21-30.png > > > On the latest openshift login wizard inside JBT, the checkbox in the last line about whether you want to save credential is truncated. Please refer to the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21681) Truncated lines seen on openshift login page

by Xia Zhao (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21681?page=com.atlassian.jira.plugi... ] Xia Zhao updated JBIDE-21681: ----------------------------- Description: On the latest openshift login wizard inside JBT, the checkbox in the last line about whether you want to save credential is truncated. Please refer to the attached screenshot. > Truncated lines seen on openshift login page > -------------------------------------------- > > Key: JBIDE-21681 > URL: https://issues.jboss.org/browse/JBIDE-21681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.CR1-v20160212-1935-B177 > OS: Fedora 17 & 22 > Reporter: Xia Zhao > Priority: Minor > Labels: login_wizard, openshift_v3 > Attachments: Screenshot from 2016-02-15 10-21-30.png > > > On the latest openshift login wizard inside JBT, the checkbox in the last line about whether you want to save credential is truncated. Please refer to the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21681) Truncated lines seen on openshift login page

by Xia Zhao (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21681?page=com.atlassian.jira.plugi... ] Xia Zhao updated JBIDE-21681: ----------------------------- Description: (was: No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.) > Truncated lines seen on openshift login page > -------------------------------------------- > > Key: JBIDE-21681 > URL: https://issues.jboss.org/browse/JBIDE-21681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.CR1-v20160212-1935-B177 > OS: Fedora 17 & 22 > Reporter: Xia Zhao > Priority: Minor > Labels: login_wizard, openshift_v3 > Attachments: Screenshot from 2016-02-15 10-21-30.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3595) dark theme not nice

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3595?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3595: -------------------------------------- Component/s: upstream > dark theme not nice > ------------------- > > Key: JBDS-3595 > URL: https://issues.jboss.org/browse/JBDS-3595 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 9.1.0.Beta2 > Reporter: Aleksandar Kostadinov > Attachments: jbds_dark.png > > > Selecting "Dark" them in appearance yields somehow ugly result. Would be nice to be fixed. > !jbds_dark.png|thumbnail! > btw have installed GoClipse, not sure if that matters. Have not checked dark theme before install. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21665) Scaling OS3 application does not work properly

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21665?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21665: --------------------------------------------- are you talking about the main text editors content getting updated ? Then there are few approaches. 1) just pick up the new content and set it directly - sucks for users that have been editing 2) inform the user the config changed - do you want to reload the latest data (and tell him he will loose any changes) I think we should do #1 if user has no edits, if the user has done some editing do #2. Also, user should be able in #2 to tell it to stop bugging him for that edit session. btw. I assume by "not being able to save" is something we let the server decide if the changes he have can be saved - not something we will prevent from the IDE side to attempt. in case he actually got the right ocntent save should be fine to do, right ? > Scaling OS3 application does not work properly > ---------------------------------------------- > > Key: JBIDE-21665 > URL: https://issues.jboss.org/browse/JBIDE-21665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Attachments: edit_error.png > > > When I am trying to scale application via tooling, first attempt to set replicas amount works but every consecutive attempt to edit same resource fails. See following screenshot of the error followed by stack trace > !edit_error.png! > {code} > com.openshift.restclient.OpenShiftException: Could not update resource eap-app-1: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:480) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:247) > at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:92) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.restclient.http.HttpClientException: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:226) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:191) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:119) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:243) > ... 2 more > Caused by: java.io.IOException: Server returned HTTP response code: 409 for URL: https://10.1.2.2:8443/api/v1/namespaces/project01/replicationcontrollers/... > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:187) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016