April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3824) Installer: it is not clear what will be downloaded on Confirmation page

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3824?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3824: ------------------------------ Affects Version/s: 9.1.0.CR1 (was: 9.1.0.GA) > Installer: it is not clear what will be downloaded on Confirmation page > ----------------------------------------------------------------------- > > Key: JBDS-3824 > URL: https://issues.jboss.org/browse/JBDS-3824 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Labels: havoc > > While on the _Confirmation_ page inside installer, there is a button _Download & Install_. User already downloaded 1.5G installer and it's not clear what will be downloaded in the next step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3829) Installer does not start properly when the user has control characters in the name

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3829?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3829: ------------------------------ Affects Version/s: 9.1.0.CR1 (was: 9.1.0.GA) > Installer does not start properly when the user has control characters in the name > ---------------------------------------------------------------------------------- > > Key: JBDS-3829 > URL: https://issues.jboss.org/browse/JBDS-3829 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > > Surprisingly, windows allows usernames such as n&o#t.e-r!u(e)r > With such a name, the installer does not even load the first page. It looks like it can't load some file, but I didn't get any error message out of it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3822: ------------------------------ Affects Version/s: 9.1.0.CR1 (was: 9.1.0.GA) > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Labels: havoc > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3810) Link to developers.redhat.com on the first page opens in the main window

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3810?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3810: ------------------------------ Affects Version/s: 9.1.0.CR1 (was: 9.1.0.GA) > Link to developers.redhat.com on the first page opens in the main window > ------------------------------------------------------------------------ > > Key: JBDS-3810 > URL: https://issues.jboss.org/browse/JBDS-3810 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc > Attachments: screenshot-1.png > > > The link to developers.redhat.com in the description paragraph on login page opens the developers page in the main window. Since the browser controls are disabled by default, there is no way to get back to the installer pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3811) Register/forgot login links don't respond when login form is empty and no error message is present yet

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3811?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3811: ------------------------------ Affects Version/s: 9.1.0.CR1 (was: 9.1.0.GA) > Register/forgot login links don't respond when login form is empty and no error message is present yet > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3811 > URL: https://issues.jboss.org/browse/JBDS-3811 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Joshua Wilson > Labels: havoc, ui > > Open the installer -> focus is on the username field. > Click one of the links below the form -> the error message saying the form is empty appears, but the web page doesn't open. You have to click a second time for it to respond. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22152: ------------------------------------ Launches are not removed from the Debug view automatically. I tried with a simple Java application. If you delete the corresponding launch configuration, then you got the same result. !!BeforeDeleteLaunchConfiguration.png|thumbnail!! !AfterDeleteLaunchConfiguration.png|thumbnail! Just checking why we don't see a tree > Unknown launch is left in Debug view after deletion of an OS 3 server adapter > ----------------------------------------------------------------------------- > > Key: JBIDE-22152 > URL: https://issues.jboss.org/browse/JBIDE-22152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Minor > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png > > > When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them. > !launches.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22152: ------------------------------- Attachment: AfterDeleteLaunchConfiguration.png BeforeDeleteLaunchConfiguration.png > Unknown launch is left in Debug view after deletion of an OS 3 server adapter > ----------------------------------------------------------------------------- > > Key: JBIDE-22152 > URL: https://issues.jboss.org/browse/JBIDE-22152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Minor > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png > > > When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them. > !launches.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13303) errors in error log when navigating openshift explorer and no connection setup

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13303?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13303: -------------------------------- Fix Version/s: 4.4.x (was: 4.2.x) (was: 4.3.x) > errors in error log when navigating openshift explorer and no connection setup > ------------------------------------------------------------------------------ > > Key: JBIDE-13303 > URL: https://issues.jboss.org/browse/JBIDE-13303 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.x > > > Open openshift explorer with properties view and no connection open and no network attached. > com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.UnknownHostException: openshift.redhat.com > at com.openshift.internal.client.RestService.request(RestService.java:103) > at com.openshift.internal.client.RestService.request(RestService.java:91) > at com.openshift.internal.client.RestService.request(RestService.java:72) > at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:135) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:104) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199) > at org.jboss.tools.openshift.express.internal.ui.property.UserPropertySource$1.run(UserPropertySource.java:112) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.net.UnknownHostException: openshift.redhat.com > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:194) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:99) > at com.openshift.internal.client.RestService.request(RestService.java:139) > at com.openshift.internal.client.RestService.request(RestService.java:97) > ... 9 more > Caused by: java.net.UnknownHostException: openshift.redhat.com > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491) > at java.security.AccessController.doPrivileged(Native Method) > at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177) > ... 12 more > Caused by: java.net.UnknownHostException: openshift.redhat.com > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432) > at java.net.Socket.connect(Socket.java:529) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570) > at sun.net.NetworkClient.doConnect(NetworkClient.java:158) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:523) > at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272) > at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94) > ... 11 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14632?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14632: -------------------------------- Fix Version/s: 4.4.x (was: 4.2.x) (was: 4.3.x) > 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 > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-664) add TransformationToolsTest, refactor Criteria Builder, Expression builder, Reconciler

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-664?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-664: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/695, https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/696 (was: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/695) > add TransformationToolsTest, refactor Criteria Builder, Expression builder, Reconciler > --------------------------------------------------------------------------------------- > > Key: JBTIS-664 > URL: https://issues.jboss.org/browse/JBTIS-664 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Beta1, 4.2.6.CR2 > > -- 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 April 2016