[JBoss JIRA] (JBIDE-12982) Using OpenShift Wizard on existing Project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12982?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-12982.
--------------------------------------
Fix Version/s: 4.1.0.Alpha1
(was: 4.0.x)
Resolution: Cannot Reproduce Bug
I cannot reproduce this, closing it as *Cannot reproduce*
> Using OpenShift Wizard on existing Project
> ------------------------------------------
>
> Key: JBIDE-12982
> URL: https://issues.jboss.org/browse/JBIDE-12982
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Beta1
> Environment: Mac OSX Lion - Java 7 - 32-bit (based on JBDS Installer)
> Reporter: Burr Sutter
> Assignee: Burr Sutter
> Fix For: 4.1.0.Alpha1
>
>
> I have an existing application on OpenShift
> http://mobile-html5.rhcloud.com/
> I have a brand new installation of JBDS6 Beta1 with a brand new workspace.
> I wish to the OpenShift App Wizard (JBoss Central) to git clone the already hosted OpenShift app into my local workspace. This process either hangs or when it does complete it does not show my app in the Project Explorer nor does it show the Server Adapter under the Servers Tab.
> The project does seem to be git cloned when using Finder/File Explorer.
> This video shows the hanging
> http://screencast.com/t/6rrqYBBfqrq
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-13020) Have to prompt user to upload keys like we do when no domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13020?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13020:
------------------------------------------
set to Minor since this is not blocking users, this is about a nice little enhancement that would improve usability
> Have to prompt user to upload keys like we do when no domain
> ------------------------------------------------------------
>
> Key: JBIDE-13020
> URL: https://issues.jboss.org/browse/JBIDE-13020
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: create-domain-first.png, no-keys-yet.png
>
>
> We currently error in the git configuration page of the application wizard if the user did not add any keys to his OpenShift account:
> !no-keys-yet.png!
> He can then hit the "SSH Keys Wizard" link, get to the ssh keys management wizard and upload a key. The error will then go away and the user can process, create/import his application.
> We should not error, we should prompt the user to upload keys if we see that he has none (on OpenShift) so far. We do the very same with the domain. If the user launches the wizard, he'll get a dialog that asks him to create a domain. The application wizard will only appear on successfull creation of the domain.
> !create-domain-first.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-13293) NPE when deleting an application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13293?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13293:
-------------------------------------
Fix Version/s: 4.1.0.Alpha1
> NPE when deleting an application
> --------------------------------
>
> Key: JBIDE-13293
> URL: https://issues.jboss.org/browse/JBIDE-13293
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha1
>
>
> Error occurred when deleting an OpenShift application from the OpenShift Explorer view:
> java.lang.NullPointerException
> at org.eclipse.ui.internal.progress.ProgressInfoItem.getJobNameAndStatus(ProgressInfoItem.java:443)
> at org.eclipse.ui.internal.progress.ProgressInfoItem.refresh(ProgressInfoItem.java:578)
> at org.eclipse.ui.internal.progress.ProgressInfoItem.createChildren(ProgressInfoItem.java:304)
> at org.eclipse.ui.internal.progress.ProgressInfoItem.<init>(ProgressInfoItem.java:204)
> at org.eclipse.ui.internal.progress.DetailedProgressViewer.createNewItem(DetailedProgressViewer.java:203)
> at org.eclipse.ui.internal.progress.DetailedProgressViewer.add(DetailedProgressViewer.java:177)
> at org.eclipse.ui.internal.progress.ProgressViewerContentProvider.add(ProgressViewerContentProvider.java:224)
> at org.eclipse.ui.internal.progress.ProgressViewUpdater$1.runInUIThread(ProgressViewUpdater.java:285)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3944)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3621)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:364)
> at org.eclipse.jface.dialogs.MessageDialog.openConfirm(MessageDialog.java:417)
> at org.jboss.tools.openshift.express.internal.ui.action.DeleteApplicationAction.run(DeleteApplicationAction.java:66)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-13020) Have to prompt user to upload keys like we do when no domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13020?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13020:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.0.x)
> Have to prompt user to upload keys like we do when no domain
> ------------------------------------------------------------
>
> Key: JBIDE-13020
> URL: https://issues.jboss.org/browse/JBIDE-13020
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
> Attachments: create-domain-first.png, no-keys-yet.png
>
>
> We currently error in the git configuration page of the application wizard if the user did not add any keys to his OpenShift account:
> !no-keys-yet.png!
> He can then hit the "SSH Keys Wizard" link, get to the ssh keys management wizard and upload a key. The error will then go away and the user can process, create/import his application.
> We should not error, we should prompt the user to upload keys if we see that he has none (on OpenShift) so far. We do the very same with the domain. If the user launches the wizard, he'll get a dialog that asks him to create a domain. The application wizard will only appear on successfull creation of the domain.
> !create-domain-first.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months