March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19522) Snapshot wizard: Snapshot restore app from different type archive does not pop up with failure info .

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19522?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19522. ------------------------------------ > Snapshot wizard: Snapshot restore app from different type archive does not pop up with failure info . > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-19522 > URL: https://issues.jboss.org/browse/JBIDE-19522 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.CR1 > Environment: JBoss Developer Studio 8.1.0 Beta1 > Reporter: Yanping Zhang > Assignee: Andre Dietisheim > Labels: openshift_v2, snapshot_wizard > Fix For: 4.5.3.Final > > > [~yanpzhan] if you get the info in the console that the snapshot could be restored (the server is reporting in the console, not the tooling), so I would think that this is a bug in the server? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12144) EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12144?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-12144. ------------------------------------ > EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-12144 > URL: https://issues.jboss.org/browse/JBIDE-12144 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: cleanup, openshift_v2 > Fix For: 4.5.3.Final > > > EgitUtils#push throws an exception if the push failed because of ex. "non fastforward push". > {code} > private static PushOperationResult push(Repository repository, RemoteConfig remoteConfig, boolean force, IProgressMonitor monitor) throws CoreException { > ... > PushOperationResult pushResult = op.getOperationResult(); > if (hasFailedEntries(pushResult)) { > throw new CoreException( > EGitCoreActivator.createErrorStatus( > NLS.bind("Could not push repository {0}: {1}", > repository.toString(), getErrors(pushResult)) > , null)); > } > return pushResult; > {code} > EGit is not throwing an exception in this case. You simply get the failure in the PushResult object you'll have to look at. > EGitUtils#push is thus changing the API semantics of EGit and it shouldn't. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18665) Application wizard: Should not use project-name as application name if it's invalid, should sanitze it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18665?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-18665. ------------------------------------ > Application wizard: Should not use project-name as application name if it's invalid, should sanitze it > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18665 > URL: https://issues.jboss.org/browse/JBIDE-18665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > Attachments: non-alphanumeric-application-name.png > > > In JBIDE-18052 we started using the project name as suggested application name. If the project name is using non-alphanumeric characters, the suggested application name is invalid. We should not suggest invalid application names, we should sanitize those names before suggesting those. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20636) Push changes: Management interface wont come up while deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20636?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20636. ------------------------------------ > Push changes: Management interface wont come up while deployment > ---------------------------------------------------------------- > > Key: JBIDE-20636 > URL: https://issues.jboss.org/browse/JBIDE-20636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.5.3.Final > > > Reference: https://github.com/openshift/origin/issues/4502 > {code} > Preparing build for deployment > Deployment id is f2c69660 > Activating deployment > Starting PHPMyAdmin cartridge > Starting MySQL 5.5 cartridge Deploying JBoss > Starting jbossas cartridge > Found 127.3.158.129:8080 listening port > Found 127.3.158.129:9999 listening port > CLIENT_MESSAGE: Could not connect to JBoss management interface, skipping deployment verification > ------------------------- > Git Post-Receive Result: success > Activation status: success > Deployment completed with status: success > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19971. ------------------------------------ > OSE v2 prompts user to enter kerberos credentials from command line while importing an application > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19971 > URL: https://issues.jboss.org/browse/JBIDE-19971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v2 > Fix For: 4.5.3.Final > > Attachments: authorized.png, creds_prompt.png, jstack.txt, krb5-auth-method-is-1st.png > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there. > Prompt from CLI looks like: > Kerberos username [mlabuda]: > Kerberos password for mlabuda: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20265) Openshift: NPE appears while searching app from existing cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20265?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20265. ------------------------------------ > Openshift: NPE appears while searching app from existing cartridges > ------------------------------------------------------------------- > > Key: JBIDE-20265 > URL: https://issues.jboss.org/browse/JBIDE-20265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2 > Fix For: 4.5.3.Final > > Attachments: Screenshot 2015-07-15 13.09.08.png, Screenshot 2015-07-15 13.11.11.png > > > NPE appears while searching necessary cartridges and selecting any of them while adding new symbols into search field -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14632?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-14632. ------------------------------------ > 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 > Assignee: Andre Dietisheim > Priority: Minor > Labels: explorer, openshift_v2 > Fix For: 4.5.3.Final > > > 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 (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19654. ------------------------------------ > Application wizard: Opening the wizard on an account without SSH key opens broken wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19654 > URL: https://issues.jboss.org/browse/JBIDE-19654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > Attachments: new_app_wizard.png, prompt-to-upload-keys.png > > > If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty > !new_app_wizard.png! > There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18038) Server adapter: Switching between workspace without and with OpenShift server adapter cause invoking connection dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18038?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-18038. ------------------------------------ > Server adapter: Switching between workspace without and with OpenShift server adapter cause invoking connection dialog > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18038 > URL: https://issues.jboss.org/browse/JBIDE-18038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final > > > Switching from workspace without OpenShift server adapter to workspace with opened details for OpenShift server adapter opens connection dialog (credentials) before opening workbench. After canceling/completing this connection dialog, workbench shell is opened. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18037) Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18037?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-18037. ------------------------------------ > Server Adapter wizard, Connection wizard: Cannot select other connection in creating a new server adapter than the first one in case of not connected connection > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18037 > URL: https://issues.jboss.org/browse/JBIDE-18037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v2, server_adapter_wizard > Fix For: 4.5.3.Final > > Attachments: openshift_explorer.png, server_adapter_wizard.png > > > When creating a new server adapter there is a wizard where user can choose existing connection in case of not connected connection (e.g. after restarting Eclipse/JBDS). > !server_adapter_wizard.png! > Problem is when you are not connected to the first connection in OpenShift explorer. Than the wizard preselect the first one connection from OpenShift Explorer and others are missing in the selection - mine OpenShift explorer contains 3 connections but in the wizard mentioned above is only first one listed in the combo box. > !openshift_explorer.png! > There should be option to choose any connection and on the next wizard pages this connection could be preselected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 March 2018