[JBoss JIRA] (ERT-66) Create Identifier Completion Engine
by Ian Stewart-Binks (JIRA)
[ https://issues.jboss.org/browse/ERT-66?page=com.atlassian.jira.plugin.sys... ]
Ian Stewart-Binks edited comment on ERT-66 at 4/6/16 11:13 AM:
---------------------------------------------------------------
- Identifiers completion should also support CamelCase, i.e. if the identifier CamelCase exists and the user types in CC, CamelCase should be proposed.
- Identifiers that begin with an underscore should have a lower relevance than those that do not.
- Function completion should check if `(` already exists. If it does, do not insert `(`, if it does not, insert it.
- Note scope difference for let and var.
- Note global scope for identifiers without variable declaration keyword (ASTVisitor must now visit all nodes, and only add identifiers in if in current scope)
was (Author: istewart):
- Identifiers completion should also support CamelCase, i.e. if the identifier CamelCase exists and the user types in CC, CamelCase should be proposed.
- Identifiers that begin with an underscore should have a lower relevance than those that do not.
- Function completion should check if `(` already exists. If it does, do not insert `(`, if it does not, insert it.
- Note scope difference for let and var.
> Create Identifier Completion Engine
> -----------------------------------
>
> Key: ERT-66
> URL: https://issues.jboss.org/browse/ERT-66
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Ian Stewart-Binks
>
> When a user invokes code completion, a set of useful identifier should be suggested to them. These identifiers should only be identifiers that are visible within the current scope from the current file. This should first support identifiers using ES5 keywords, and be extensible enough for ES6 keywords to fit in later on. Function identifiers from the current file and scope should be included as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 8 or above on windows
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22078:
--------------------------------
Summary: Error publishing war file to wildfy 8 or above on windows (was: Error publishing war file to wildfy 10.0 on windows)
> Error publishing war file to wildfy 8 or above on windows
> ---------------------------------------------------------
>
> Key: JBIDE-22078
> URL: https://issues.jboss.org/browse/JBIDE-22078
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22125) Add docker connection management to deploy image wizard
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-22125:
----------------------------------
Summary: Add docker connection management to deploy image wizard
Key: JBIDE-22125
URL: https://issues.jboss.org/browse/JBIDE-22125
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Reporter: Jeff MAURY
Assignee: Jeff MAURY
Fix For: 4.4.x
clicked this nice "Deploy to openshift" menu in Openshift explorer and the dialog that shows up is just a lot of fields with no values.
Cannot create a new docker connection.
Makes it hard to get started ;/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3774?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-3774:
-----------------------------------
I just remembered something...the Login with the subscription/password is very slow and I bet I double or triple clicked the Login button as it has no "wait cursor" to indicate that it is attempting to verify/validate my credentials.
> Failed due to 2 attempts at installing CDK's vagrant box
> --------------------------------------------------------
>
> Key: JBDS-3774
> URL: https://issues.jboss.org/browse/JBDS-3774
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Environment: Windows 10 Pro
> Reporter: Burr Sutter
> Attachments: install.log, vagrant.log, vbox.log
>
>
> Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f"
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> ...
> Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2
> c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box"
> The box you're attempting to add already exists. Remove it before
> adding it again or add it with the `--force` flag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22123) NPE is thrown when no template parameter is selected and reset button is clicked
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22123?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22123:
--------------------------------
Labels: application_wizard openshift_v3 respin-b (was: application_wizard openshift_v3)
> NPE is thrown when no template parameter is selected and reset button is clicked
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22123
> URL: https://issues.jboss.org/browse/JBIDE-22123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: application_wizard, openshift_v3, respin-b
> Fix For: 4.3.1.CR1
>
>
> When a Reset button, to reset a template parameter, on second New OpenShift Application wizard page is clicked and there is no selection, following error pops up in error log
> {code}
> Unhandled event loop exception
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.resetParameter(NewApplicationWizardModel.java:287)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateParametersPage$7.widgetSelected(TemplateParametersPage.java:383)
> 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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> 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.GeneratedMethodAccessor81.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22123) NPE is thrown when no template parameter is selected and reset button is clicked
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22123?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22123:
-----------------------------------
Assignee: Fred Bricon
> NPE is thrown when no template parameter is selected and reset button is clicked
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22123
> URL: https://issues.jboss.org/browse/JBIDE-22123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: application_wizard, openshift_v3
>
> When a Reset button, to reset a template parameter, on second New OpenShift Application wizard page is clicked and there is no selection, following error pops up in error log
> {code}
> Unhandled event loop exception
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.resetParameter(NewApplicationWizardModel.java:287)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateParametersPage$7.widgetSelected(TemplateParametersPage.java:383)
> 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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> 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.GeneratedMethodAccessor81.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22123) NPE is thrown when no template parameter is selected and reset button is clicked
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22123?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22123:
--------------------------------
Fix Version/s: 4.3.1.CR1
> NPE is thrown when no template parameter is selected and reset button is clicked
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22123
> URL: https://issues.jboss.org/browse/JBIDE-22123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> When a Reset button, to reset a template parameter, on second New OpenShift Application wizard page is clicked and there is no selection, following error pops up in error log
> {code}
> Unhandled event loop exception
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.resetParameter(NewApplicationWizardModel.java:287)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateParametersPage$7.widgetSelected(TemplateParametersPage.java:383)
> 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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> 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.GeneratedMethodAccessor81.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22113) CDK shutdown always goes to Forcing shutdown of VM on Windows
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22113?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22113:
-------------------------------------
Don't be sorry... it's something we can watch out for at least.
> CDK shutdown always goes to Forcing shutdown of VM on Windows
> -------------------------------------------------------------
>
> Key: JBIDE-22113
> URL: https://issues.jboss.org/browse/JBIDE-22113
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> On OS X, when I stop CDK in JBDS, I get this in the console:
> ==> default: Unregistering box with vagrant-registration...
> ==> default: Attempting graceful shutdown of VM...
> And a few seconds later, the server adapter shows "Stopped".
> Today while testing on Windows I noticed that it behaves differently.
> It first displays these two lines, but it keeps "Stopping". And eventually there is another line in the console which says:
> ==> default: Forcing shutdown of VM...
> After this, the server adapter shows "Stopped".
> So for some unknown reason, on Windows the graceful shutdown fails to work.
> This is JBDS+CDK installed from the latest windows installer (built April 4th).
> It would be good to see if others see this on Windows as well or not.
> Interestingly, when I just tried "vagrant halt" from cygwin instead of in JBDS, it stops normally - graceful shutdown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years