April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19412: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Labels: connection, openshift_v3 > Fix For: 4.6.x > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25682) OpenShift view: Implement tooltip with information what user selected (if it is project/service/pod/...)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25682?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25682: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > OpenShift view: Implement tooltip with information what user selected (if it is project/service/pod/...) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25682 > URL: https://issues.jboss.org/browse/JBIDE-25682 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM1 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: explorer > Fix For: 4.6.x > > > Implement tooltip: when user selects item in OpenShift explorer there should be some kind of info/tooltip, which shows if he selects project or service or pod, different icons is not enough, if there is no legend for it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21201: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > TernError: No type found at the given position. > ----------------------------------------------- > > Key: JBIDE-21201 > URL: https://issues.jboss.org/browse/JBIDE-21201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.0.Beta1 > Environment: tern 1.1.0 > Reporter: Pavol Srna > Assignee: Victor Rubezhny > Fix For: 4.6.x > > > 1. Create JSF 1.2 Kick Start project > 2. Open inputUserName.jsp in VPE > 3. Click on 'user' text within <h:inputText> tag > 4. Press F3 key > {code} > tern.TernException: TernError: No type found at the given position. > at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) > at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) > ... 2 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24390) Items hidden by filter are excluded from installation

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24390?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24390: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Items hidden by filter are excluded from installation > ----------------------------------------------------- > > Key: JBIDE-24390 > URL: https://issues.jboss.org/browse/JBIDE-24390 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.4.Final > Reporter: Lukáš Valach > Priority: Minor > Fix For: 4.6.x > > > Items which are hidden by filter won't be installed even if they are selected. > For example: > # Open Red Hat Central > # Click "Select All" > # Type into "Find" field "angular" > # The only one item are now displayed and button "Install/Update (1)" shows that only one item are selected to be installed which isn't true. All items are still selected though only one of them are shown. > # Click "Install/Update (1)" then you will see that only Angular is going to be installed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18240) Show in Forge Console should ask to start forge if forge is not started

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18240?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18240: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Show in Forge Console should ask to start forge if forge is not started > ----------------------------------------------------------------------- > > Key: JBIDE-18240 > URL: https://issues.jboss.org/browse/JBIDE-18240 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25683) OpenShift New Connection: Automatic copying of token does not work on Fedora

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25683?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25683: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > OpenShift New Connection: Automatic copying of token does not work on Fedora > ---------------------------------------------------------------------------- > > Key: JBIDE-25683 > URL: https://issues.jboss.org/browse/JBIDE-25683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM1 > Environment: F27 > Red Hat JBoss Developer Studio > Version: 11.3.0.AM1 > Build id: AM1-v20180201-0838-B1971 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.6.x > > > Automac copying of token does not work on Fedora, but it does on Win10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22756) Connection: various weirdness in token/password implementations

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22756?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22756: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Connection: various weirdness in token/password implementations > --------------------------------------------------------------- > > Key: JBIDE-22756 > URL: https://issues.jboss.org/browse/JBIDE-22756 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Labels: connection > Fix For: 4.6.x > > > The lifecycle of the token is rather weird and needs a consistent logic: > When connecting via wizard the token is set in the connection wizard: > {code:title=ConnectionWizardPageModel#connect} > ... > try { > IConnection connection = createConnection(connectionFactory, connectionAuthenticationProvider); > ... > {code} > {code:title=ConnectionWizardPageModel#createConnection} > ... > if (authProvider != null) { > authProvider.update(connection); // sets the token > } > ... > {code} > {code:title=BearTokenAuthenticationProvider#update} > ... > connection.setAuthScheme(IAuthorizationContext.AUTHSCHEME_OAUTH); > connection.setToken(tokenObservable.getValue()); > connection.setRememberToken(rememberTokenObservable.getValue()); > ... > {code} > {code:title=Connection#connect} > if(authorize()) { > ... > {code} > {code:title=Connection#authorized} > ... > if (context.isAuthorized()) { > String username = context.getUser().getName(); > String token = context.getToken(); > updateAuthorized(username, token); > } else { > ... > {code} > The token is then fetched from client and set to the connection > {code:title=Connection#updateAuthorized} > setToken(token); > ... > {code} > and the password is cleared > {code:Connectoin#savePasswordOrToken} > } else if (IAuthorizationContext.AUTHSCHEME_OAUTH.equals(getAuthScheme())){ > boolean success = saveOrClear(SECURE_STORAGE_TOKEN_KEY, this.token, isRememberToken()); > if(success) { > //Avoid second secure storage prompt. > //Token is stored, password should be cleared. > clearPassword(); > {code} > I suspect the aim here is to clear existing password in secure storage if the user is switching password->token based auth (and vice versa) > The opposite is then not fully congruent. The token is only cleared in secure storage, not in Connection instance var > {code:title=Connection#savePasswordOrToken} > if (IAuthorizationContext.AUTHSCHEME_BASIC.equals(getAuthScheme())) { > boolean success = saveOrClear(SECURE_STORAGE_PASSWORD_KEY, this.password, isRememberPassword()); > if (success) { > //Avoid second secure storage prompt. > // Password is stored, token should be cleared. > clearToken(); > } > {code:Connection#clearToken} > // dont clear the token instance var: JBIDE-22594 > setRememberToken(false); > saveOrClear(SECURE_STORAGE_TOKEN_KEY, null, false); > {code} > I suspect that we should only clear in secure storage, not in the Connection instance as we see in JBIDE-22594 (for the opposite case where we dont clear the token in the Connection instance). But then one has to keep in mind that all auth is token based. Even if you auth via password initially, the auth is then switched to token based once the authorization succeeded and we got a token: > {code:title=Connection#updateAuthorized} > setToken(token); > if (IAuthorizationContext.AUTHSCHEME_OAUTH.equalsIgnoreCase(getAuthScheme())) { > setUsername(username); > } > // force auth strategy to token if authorized > TokenAuthorizationStrategy tokenStrategy = new TokenAuthorizationStrategy(token, username); > client.setAuthorizationStrategy(tokenStrategy); > {code} > Another issue is that the connection and the auth schemeare both stored in different classes. The connection is stored via > {code:title=ConnectionPersistency#persist} > preferences.saveConnections(connections.keySet().toArray(new String[] {})); > ... > {code} > while the auth scheme is stored in Connection#saveAuthSchemePreference: > {code:title=Connection#connect} > saveAuthSchemePreference(); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19087) Debugging Ionic Project With CordovaSim and Livereload

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19087?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19087: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Debugging Ionic Project With CordovaSim and Livereload > ------------------------------------------------------ > > Key: JBIDE-19087 > URL: https://issues.jboss.org/browse/JBIDE-19087 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.2.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.6.x > > > The issue was created on top of the thread on developer.jboss.org - https://developer.jboss.org/thread/251880 > Basically, the issue is tightly coupled with the upstream - https://github.com/driftyco/ionic/issues/3222 (ionic history state lose). > *Upstream issue:* https://github.com/driftyco/ionic/issues/3222 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23403) As a user I need to be able to inspect the state of my EAP deployments

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23403?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23403: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > As a user I need to be able to inspect the state of my EAP deployments > ---------------------------------------------------------------------- > > Key: JBIDE-23403 > URL: https://issues.jboss.org/browse/JBIDE-23403 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server, web_console > Fix For: 4.6.x > > > The web console for eap was disabled in the eap image that we have in OpenShift. It's therefore not possible for users to inspect the state of their deployment. > The only there is to do such thing is to inspect jolokia informations. There is no such tooling in Eclipse yet. Furthermore the url to access those is non-obvious as one can see [here|http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-...]. I therefore suggest that we should provide help/tooling that allows users to easily access and manipulate those informations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17577) Wrong layout of Back and Forward buttons with GTK 3 and Java 8

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17577?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-17577: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Wrong layout of Back and Forward buttons with GTK 3 and Java 8 > -------------------------------------------------------------- > > Key: JBIDE-17577 > URL: https://issues.jboss.org/browse/JBIDE-17577 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0 Beta2-v20140608-1040-B121 > Oracle JDK 1.8.0_05 > Fedora 20 64bit Gnome > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.6.x > > Attachments: browsersimlayout.png > > > 1. Select GTK3 in Windows > Preferences > BrowserSim/CordovaSim > 2. Open BrowserSIm > 3. Navigate BrowserSim to www.google.com > ERROR: Once web page is fully loaded Back button has wrong layout and Forward buttons disappears > !browsersimlayout.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

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 April 2018