September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-14632) Explorer: "could not store password" logged whenever right clicking user/navigating tree

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14632?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-14632: ------------------------------- Labels: explorer openshift_v2 (was: explorer) > Explorer: "could not store password" logged whenever right clicking user/navigating tree > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14632 > URL: https://issues.jboss.org/browse/JBIDE-14632 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: explorer, openshift_v2 > Fix For: 4.4.x > > > created connection. > get bunch of these stacktraces - especially when right clicking on the node. > {code} > org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStoreException: Could not store password > at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.storeInPreferences(SecurePasswordStore.java:102) > at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.update(SecurePasswordStore.java:56) > at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.setPassword(SecurePasswordStore.java:50) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.saveOrClearPassword(Connection.java:441) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.save(Connection.java:430) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:196) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.getDefaultDomain(Connection.java:332) > at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction.validate(DeleteDomainAction.java:47) > at org.jboss.tools.openshift.express.internal.ui.explorer.actionProvider.AbstractOpenShiftExplorerViewerActionProvider.fillContextMenu(AbstractOpenShiftExplorerViewerActionProvider.java:50) > at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:221) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:216) > at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:173) > at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:260) > at org.eclipse.ui.navigator.CommonNavigatorManager$4.menuAboutToShow(CommonNavigatorManager.java:275) > at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:343) > at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:475) > at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:470) > at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:500) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4164) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470) > at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:806) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5606) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77) > at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:278) > at org.eclipse.swt.widgets.Display.runPopups(Display.java:4087) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3642) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > Caused by: org.eclipse.equinox.security.storage.StorageException: No password provided. > at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304) > at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224) > at org.eclipse.equinox.internal.security.storage.SecurePreferences.put(SecurePreferences.java:224) > at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put(SecurePreferencesWrapper.java:110) > at org.jboss.tools.openshift.express.internal.ui.utils.SecurePasswordStore.storeInPreferences(SecurePasswordStore.java:99) > ... 52 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11367) Application wizard should close and run maven import in background once the application was created

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-11367: ------------------------------- Labels: application_wizard openshift_v2 (was: application_wizard) > Application wizard should close and run maven import in background once the application was created > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard, openshift_v2 > Fix For: LATER > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen. > We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8840) Support EL susbstitution for collections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8840?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-8840: ------------------------------ Description: Can you detail a little bit ? > Support EL susbstitution for collections > ---------------------------------------- > > Key: JBIDE-8840 > URL: https://issues.jboss.org/browse/JBIDE-8840 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 3.3.0.M1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: LATER > > > Can you detail a little bit ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23119) Webservices and Rest New and Noteworthy for 4.4.1.Final

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23119?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23119. --------------------------------- Resolution: Rejected > Webservices and Rest New and Noteworthy for 4.4.1.Final > ------------------------------------------------------- > > Key: JBIDE-23119 > URL: https://issues.jboss.org/browse/JBIDE-23119 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23109) Live Reload New and Noteworthy for 4.4.1.Final

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23109?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23109. --------------------------------- Resolution: Rejected > Live Reload New and Noteworthy for 4.4.1.Final > ---------------------------------------------- > > Key: JBIDE-23109 > URL: https://issues.jboss.org/browse/JBIDE-23109 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-859) Method isIssueClosed return true for jira which is reopened.

by Matej Kralik (JIRA)

Matej Kralik created JBTIS-859: ---------------------------------- Summary: Method isIssueClosed return true for jira which is reopened. Key: JBTIS-859 URL: https://issues.jboss.org/browse/JBTIS-859 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, teiid Affects Versions: 4.3.1.Final Reporter: Matej Kralik Assignee: Matej Kralik When jira which is opened/reopened contains link to another jira which is closed, method JiraClient().isIssueClosed() return true. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22617) Integrate DockViz in to Docker Tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22617?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-22617. ----------------------------------- Resolution: Done Resolved upstream. The new 'Image Hierarch View' shows known images and containers from a selected image or container in the other views. > Integrate DockViz in to Docker Tooling > -------------------------------------- > > Key: JBIDE-22617 > URL: https://issues.jboss.org/browse/JBIDE-22617 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Mustafa Musaji > Assignee: Xavier Coulon > Priority: Optional > Fix For: 4.4.1.Final > > > DockVIz is a tool used to provide a way to view docker information on a system in a number of ways, one of which is a tree like structure to be able to visualise docker layers. > This would be a nice thing to include in our docker toolset. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22617) Integrate DockViz in to Docker Tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22617?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22617: ---------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.x) > Integrate DockViz in to Docker Tooling > -------------------------------------- > > Key: JBIDE-22617 > URL: https://issues.jboss.org/browse/JBIDE-22617 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Mustafa Musaji > Assignee: Xavier Coulon > Priority: Optional > Fix For: 4.4.1.Final > > > DockVIz is a tool used to provide a way to view docker information on a system in a number of ways, one of which is a tree like structure to be able to visualise docker layers. > This would be a nice thing to include in our docker toolset. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4044) Use angular $http service instead of node request module

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4044?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4044: -------------------------------- Story Points: 13 > Use angular $http service instead of node request module > -------------------------------------------------------- > > Key: JBDS-4044 > URL: https://issues.jboss.org/browse/JBDS-4044 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > > Since April $http service seems to support progress reporting for http requests: > 1. See httpspec.js in this [commit|https://github.com/angular/angular.js/commit/01b18450882da9bb9c903...]; > 2. XMLHTTPRequest documentation [here|https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Usin...]. > Questions: > 1. Does it support redirects? > 2. How authentication is supported? > Benefits: > 1. Native browser service, so probably should be working faster; > 2. Proxy settings picked up from system settings, so there is no need to set up environment variables before running the installer. > Drawbacks: > 1. Proxy errors are not detectable (?) It just printed out to console without providing info trough returning error parameter for callback; > 2. No third party multi-threaded downloaders that would support restarting download from the position where it failed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4044) Use angular $http service instead of node request module

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4044?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4044: ----------------------------- > Use angular $http service instead of node request module > -------------------------------------------------------- > > Key: JBDS-4044 > URL: https://issues.jboss.org/browse/JBDS-4044 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > > Since April $http service seems to support progress reporting for http requests: > 1. See httpspec.js in this [commit|https://github.com/angular/angular.js/commit/01b18450882da9bb9c903...]; > 2. XMLHTTPRequest documentation [here|https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Usin...]. > Questions: > 1. Does it support redirects? > 2. How authentication is supported? > Benefits: > 1. Native browser service, so probably should be working faster; > 2. Proxy settings picked up from system settings, so there is no need to set up environment variables before running the installer. > Drawbacks: > 1. Proxy errors are not detectable (?) It just printed out to console without providing info trough returning error parameter for callback; > 2. No third party multi-threaded downloaders that would support restarting download from the position where it failed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016