[JBoss JIRA] (JBIDE-16849) m2e cannot parse html5 example pom after minify profile is activated
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16849?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16849:
--------------------------------
Workaround Description: Delete the <pluginManagement> node in the minify profile
Workaround: Workaround Exists
> m2e cannot parse html5 example pom after minify profile is activated
> --------------------------------------------------------------------
>
> Key: JBIDE-16849
> URL: https://issues.jboss.org/browse/JBIDE-16849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 with m2e-wro4j 1.0.2
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.2.x
>
> Attachments: wro4j.png
>
>
> {code}
> Cannot parse lifecycle mapping metadata for maven project MavenProject: org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:0.0.1-SNAPSHOT @ /files/RedHat/Workspaces/JBDS with spaces/800B1jdk7/jboss-as-kitchensink-html5-mobile/pom.xml Cause: Unrecognised tag: 'version' (position: START_TAG seen ...</artifactId>\n <version>... @8:18)
> {code}
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-9212) Consider introducing Profiles of AS Server adapteres
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9212?page=com.atlassian.jira.plugin... ]
Martin Malina closed JBIDE-9212.
--------------------------------
This JIRA can be closed. Other JIRAs have been / will be opened as necessary.
> Consider introducing Profiles of AS Server adapteres
> ----------------------------------------------------
>
> Key: JBIDE-9212
> URL: https://issues.jboss.org/browse/JBIDE-9212
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-9212a.png, JBIDE-9212b.png, JBIDE-9212c.png, JBIDE-9212d.png
>
>
> With all the different combinations of server behaviors and pollers dependent if you are runnig locally, remotely, openshift express or openshift flex it becomes hard to configure/tweak.
> Idea is to introduce the notion of profiles, provide a set of default ones users can apply in Server Wizard or even in the server editor and allow them to create new ones based on existing ones.
> These profiles would cover:
> ports, start/stop behavior, pollers, deployments and launch setup. (more?)
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-16981) Validation of @Path parameters binding ignores @PathParam fields
by Radoslav Rábara (JIRA)
Radoslav Rábara created JBIDE-16981:
---------------------------------------
Summary: Validation of @Path parameters binding ignores @PathParam fields
Key: JBIDE-16981
URL: https://issues.jboss.org/browse/JBIDE-16981
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Beta1
Reporter: Radoslav Rábara
Fix For: 4.2.0.Beta2
Validation of @Path parameters ignores @PathParam fields so if you have @PathParam field used as parameter in @Path, you get warning:
{code}The @Path template parameter '<parameter name>' is not bound to any parameter annotated with @PathParam of the '<method name>' method.{code}
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-16865) Bad server created when you hit Finish on the first page of New Server dialog
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16865?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-16865.
---------------------------------
Verified that Finish is disabled on the first page and when Finish is pressed on the second page, the server is correctly created.
(JBDS 8.0.0.Beta1a B82)
> Bad server created when you hit Finish on the first page of New Server dialog
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16865
> URL: https://issues.jboss.org/browse/JBIDE-16865
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 B78
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.Beta1
>
>
> When you go to server view -> New Server, select a type of which you already have a server+runtime and hit Finish, a server is created, but this server does not have any runtime set up and cannot be selected when e.g. creating a new html5 project.
> This probably has to do with all the changes in the server tooling, but it worked in the past. So either it should still work, or we should disable the Finish button.
> (Credits go to [~rawagner] for discovering this issue.0
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-16895) Remote EAP 6.2 fails to stop - null argument
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16895?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-16895.
---------------------------------
Verified in JBDS 8.0.0.Beta1a B82
> Remote EAP 6.2 fails to stop - null argument
> --------------------------------------------
>
> Key: JBIDE-16895
> URL: https://issues.jboss.org/browse/JBIDE-16895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 B78
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.Beta1
>
> Attachments: null-argument.png
>
>
> I cannot stop a remote server. It's EAP 6.2 without a runtime and with management operations enabled.
> When I click stop, I get this error:
> !null-argument.png!
> And this is in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-03-26 11:39:00.141
> !MESSAGE An internal error occurred during: "Stopping JBoss EAP 6.2 marvin".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.initialize(RemotePath.java:642)
> at org.jboss.ide.eclipse.as.core.util.RemotePath.<init>(RemotePath.java:197)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleNestedDeployPath(ModuleDeploymentPrefsUtil.java:159)
> at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleTreeDestinationFullPath(ModuleDeploymentPrefsUtil.java:65)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ModuleDeployPathController.getDeployDirectory(ModuleDeployPathController.java:110)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getDeploymentLocation(DeployableServer.java:254)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.getDeployLocationFolders(AbstractDeploymentScannerAdditions.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:76)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:242)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3670)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3627)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> There is no way to stop the server - you can try as many times as you like to click Stop, but each time you get the error and the server is still started.
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-16849) m2e cannot parse html5 example pom after minify profile is activated
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16849?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16849:
--------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Beta2)
> m2e cannot parse html5 example pom after minify profile is activated
> --------------------------------------------------------------------
>
> Key: JBIDE-16849
> URL: https://issues.jboss.org/browse/JBIDE-16849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 with m2e-wro4j 1.0.2
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.2.x
>
> Attachments: wro4j.png
>
>
> {code}
> Cannot parse lifecycle mapping metadata for maven project MavenProject: org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:0.0.1-SNAPSHOT @ /files/RedHat/Workspaces/JBDS with spaces/800B1jdk7/jboss-as-kitchensink-html5-mobile/pom.xml Cause: Unrecognised tag: 'version' (position: START_TAG seen ...</artifactId>\n <version>... @8:18)
> {code}
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-16849) m2e cannot parse html5 example pom after minify profile is activated
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16849?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16849:
-------------------------------------
WFK 2.5 archetype still contains the broken lifecycle mapping :-/
> m2e cannot parse html5 example pom after minify profile is activated
> --------------------------------------------------------------------
>
> Key: JBIDE-16849
> URL: https://issues.jboss.org/browse/JBIDE-16849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1 with m2e-wro4j 1.0.2
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.2.0.Beta2
>
> Attachments: wro4j.png
>
>
> {code}
> Cannot parse lifecycle mapping metadata for maven project MavenProject: org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:0.0.1-SNAPSHOT @ /files/RedHat/Workspaces/JBDS with spaces/800B1jdk7/jboss-as-kitchensink-html5-mobile/pom.xml Cause: Unrecognised tag: 'version' (position: START_TAG seen ...</artifactId>\n <version>... @8:18)
> {code}
--
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
12 years, 3 months
[JBoss JIRA] (JBDS-2899) Cannot run internal browser on RHEL6 with JBDS8.alpha2
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2899?page=com.atlassian.jira.plugin.... ]
Snjezana Peco commented on JBDS-2899:
-------------------------------------
[~ldimaggio]
Have you installed the libstdc++.so.5 library?
yum install compat-libstdc++-33
I think this issue isn't related to GTK3 because it isn't included into RHEL6.
> Cannot run internal browser on RHEL6 with JBDS8.alpha2
> ------------------------------------------------------
>
> Key: JBDS-2899
> URL: https://issues.jboss.org/browse/JBDS-2899
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration
> Affects Versions: 8.0.0.Alpha2
> Environment: RHEL6
> OpenJDK 1.7
> JBDS8.alpha2
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: respin-b
> Fix For: 8.0.0.Beta1
>
> Attachments: mac_browser.png, rhel_browser.png
>
>
> When the internal browser is opened, this error is raised:
> The embedded browser widget for this editor cannot be created. It is either not available for your operating system or the system needs to be configured in order to support embedded browser.
> No more handles [Could not detect registered XULRunner to use]
> org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use]
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:704)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.eclipse.ui.internal.browser.BrowserViewer.<init>(BrowserViewer.java:224)
> at org.eclipse.ui.internal.browser.WebBrowserView.createPartControl(WebBrowserView.java:48)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:138)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:155)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:319)
> 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:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:958)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:642)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$6.run(PartRenderingEngine.java:527)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:512)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:61)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:958)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:642)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:95)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:185)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4559)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:208)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:499)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:466)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:657)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:637)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:591)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:580)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1077)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1180)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1169)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4069)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4066)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4041)
> at org.eclipse.ui.handlers.ShowViewHandler.openView(ShowViewHandler.java:126)
> at org.eclipse.ui.handlers.ShowViewHandler.openOther(ShowViewHandler.java:99)
> at org.eclipse.ui.handlers.ShowViewHandler.execute(ShowViewHandler.java:67)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:163)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:222)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.ShowViewMenu$3.run(ShowViewMenu.java:141)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:588)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:505)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:415)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> 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:606)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
--
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
12 years, 3 months