[JBoss JIRA] (JBIDE-20026) Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20026 at 6/2/16 4:07 PM:
------------------------------------------------------------------
[~scabanovich] thanks for the PR, but as discussed with [~fbricon] we could select the connection type of the connection that was last used. The last used connection is available from ConnectionsRegistry#getRecentConnection. To set it's type to the connection type in the connection wizard you can get the matching IConnectionFactory from ConnectionsFactory#getByConnection.
The connection wizard isnt saving the most recently used connection though. The code for it is commented, while the ConnectionsRegistry has the persistence implemented.
But this isnt urgent for 4.4.0.Final
was (Author: adietish):
[~scabanovich] thanks for the PR, but as discussed with [~fbricon] we could select the connection type of the connection that was last used. The last used connection is available from ConnectionsRegistry#getRecentConnection. To set it's type to the connection type in the connection wizard you can get the matching IConnectionFactory from ConnectionsFactory#getByConnection.
But this isnt urgent for 4.4.0.Final
> Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20026) Explorer: create new connection should default to OpenShift v3 type connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20026:
------------------------------------------
[~scabanovich] thanks for the PR, but as discussed with [~fbricon] we could select the connection type of the connection that was last used. The last used connection is available from ConnectionsRegistry#getRecentConnection. To set it's type to the connection type in the connection wizard you can get the matching IConnectionFactory from ConnectionsFactory#getByConnection.
But this isnt urgent for 4.4.0.Final
> Explorer: create new connection should default to OpenShift v3 type connection
> ------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20026) Explorer: create new connection should default to OpenShift v3 type connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-20026:
----------------------------------------
Assignee: (was: Andre Dietisheim)
> Explorer: create new connection should default to OpenShift v3 type connection
> ------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20026) Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20026:
-------------------------------------
Summary: Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection (was: Explorer: create new connection should default to OpenShift v3 type connection)
> Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20026) Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20026:
-------------------------------------
Labels: connection_wizard openshift_v3 (was: openshift_v3)
> Explorer, Connection wizard: create new connection should default to OpenShift v3 type connection
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22492) For JBIDE 4.4.0.Final: Prepare for Final/GA [Webservices]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22492?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-22492.
---------------------------------
Resolution: Done
Done
{code}
$> git push origin jbosstools-4.4.x
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 341 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
To git@github.com:jbosstools/jbosstools-webservices.git
* [new branch] jbosstools-4.4.x -> jbosstools-4.4.x
{code}
> For JBIDE 4.4.0.Final: Prepare for Final/GA [Webservices]
> ---------------------------------------------------------
>
> Key: JBIDE-22492
> URL: https://issues.jboss.org/browse/JBIDE-22492
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Final
>
>
> For JBIDE 4.4.0.Final [Webservices]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch
> 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.x
> git push origin jbosstools-4.4.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!)
> * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
> 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22301) Application wizard: NPE from eclipse project with no remote git reference.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22301:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1140, https://github.com/jbosstools/jbosstools-openshift/pull/1205 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1140)
> Application wizard: NPE from eclipse project with no remote git reference.
> --------------------------------------------------------------------------
>
> Key: JBIDE-22301
> URL: https://issues.jboss.org/browse/JBIDE-22301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha2
>
> Attachments: paramter-page-invalid.png
>
>
> Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE:
> {noformat:title=Unhandled event loop exception}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22301) Application wizard: NPE from eclipse project with no remote git reference.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22301:
------------------------------------------
A minor glitch still exists, filed it to JBIDE-22511
Thanks for the fix!
Merged it into master.
> Application wizard: NPE from eclipse project with no remote git reference.
> --------------------------------------------------------------------------
>
> Key: JBIDE-22301
> URL: https://issues.jboss.org/browse/JBIDE-22301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha2
>
> Attachments: paramter-page-invalid.png
>
>
> Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE:
> {noformat:title=Unhandled event loop exception}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months