March 2018 - jbosstools-issues - Jboss List Archives

[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 reassigned JBIDE-12144: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > 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, LATER > > > 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-17903) Explorer, Server Adapter: add show in > project explorer for openshift apps

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17903?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-17903: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > Explorer, Server Adapter: add show in > project explorer for openshift apps > --------------------------------------------------------------------------- > > Key: JBIDE-17903 > URL: https://issues.jboss.org/browse/JBIDE-17903 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Labels: explorer, openshift_v2, server_adapter > Fix For: 4.5.3.Final, LATER > > > couldn't we have "show in" project explorer enabled for openshift applications ? > If 0 found -> open dialog "Application 'xyz' not found in workspace. Do you want to import it ?" > if 1 found -> have it selected in project explorer > if >1 found -> open dialog "Multiple projects found mapped to application 'xyz' which one do you want ?" (is this even technically possible since the project names would be the same...? - I guess if they are on different branches with different .project names then yes) > maybe just pick the first found in the >1 found case to keep it simple? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21137) Consistency of sorting in EmbedCartridgesJob

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21137?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21137: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > Consistency of sorting in EmbedCartridgesJob > -------------------------------------------- > > Key: JBIDE-21137 > URL: https://issues.jboss.org/browse/JBIDE-21137 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2 > Fix For: 4.5.3.Final, LATER > > > Sorting with CartridgeAddRemovePriorityComparator implies that cartridges should be stored in IApplication in a specific order, for instance, "mysql" should precede all other cartridges. If Edit Embedded Cartridges wizard is run once, the desirable order is guaranteed. However, if wizard is run twice, with "postgresql" selected on the first run and "mysql" added on the second run, the cartridges will be added to IApplication unsorted by the comparator. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-11367: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > 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 > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final, 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 (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 reassigned JBIDE-18037: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > 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, LATER > > 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

[JBoss JIRA] (JBIDE-10788) Server Adapter: Add setting ui for openshift source servers to use wtp context root if required

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10788?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-10788: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > Server Adapter: Add setting ui for openshift source servers to use wtp context root if required > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-10788 > URL: https://issues.jboss.org/browse/JBIDE-10788 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 3.3.0.M5 > Reporter: Rob Stryker > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final, LATER > > > link to JBIDE-10514 , a UI is required for this setting. > 1. Create a new application in wizard and allow to create a new project in the workspace > 2. Fix all the bugs so that it compiles (delete modules.jsp, add java version 1.6 to pom.xml, reload project configuration) > 3. Modify all your build stuff so the project does NOT deploy to root > 4. Change your context root to match what your setting is in the build > 5. Right click the project and select Run as... + Run on server > 6. Choose associated openshift server > 7. Result - No page found due to the incorrect URL. It's still using root instead of your new custom context root > A UI is required for this setting -- 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 reassigned JBIDE-18038: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > 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, LATER > > > 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-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 reassigned JBIDE-14632: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > 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, LATER > > > 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-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 reassigned JBIDE-20636: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > 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, LATER > > > 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-18866) Application wizard: allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18866?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-18866: ---------------------------------------- Fix Version/s: 4.5.3.Final Assignee: Andre Dietisheim > Application wizard: allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18866 > URL: https://issues.jboss.org/browse/JBIDE-18866 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy, openshift_v2 > Fix For: 4.5.3.Final, LATER > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges > The exact form is documented in the github (and general purpose git-) documentation: https://gist.github.com/grawity/4392747 > {quote} > SSH, aka git(a)github.com: or ssh://git@github.com/ > {quote} -- 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