[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22079:
------------------------------------------
[~mlabuda] ok we're on the same bandwagon. I feel like while this is a worthwhile enhancement enhancement to fix something that's annoying, it's not really a bug. It's an inherent problem that also exists in other parts of Eclipse. This being said this isnt critical enough for being worth a respin in 4.3.CR1. I'll thus postpone this to 4.4.0.Alpha1
> Error when import a project already existing in workspace
> ---------------------------------------------------------
>
> Key: JBIDE-22079
> URL: https://issues.jboss.org/browse/JBIDE-22079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: import-error.png
>
>
> When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear).
> Error:
> {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts.
> One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again.
> An exception stack trace is not available.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 10.0 on windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22078:
-----------------------------------
Labels: respin-b (was: )
> Error publishing war file to wildfy 10.0 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-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22057 at 4/5/16 4:06 PM:
------------------------------------------------------------------
[~scabanovich] out of my guts I'd think that this is cause. As far as I can remember we edit the dc, enable debugging in the env vars and specify the debug port. This then triggers a new deployment of a fresh pod which of course wont have the changes that we synced to it.
If this turns out to be true then this would mean that we'd have to do an initial rsync when restarting in debug mode I think
was (Author: adietish):
[~scabanovich] out of my guts I'd think that this is cause (as far as I can remember we debuggin to enabled in the env vars and also specify the debug port in the dc).
If this turns out to be true then this would mean that we'd have to do an initial rsync when restarting in debug mode I think
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3, respin-b, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22057:
-----------------------------------
Assignee: Fred Bricon
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3, respin-b, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22057:
-----------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.4.0.Alpha1)
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, respin-b, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22057:
-----------------------------------
Labels: openshift_v3 respin-b server_adapter (was: openshift_v3 server_adapter)
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, respin-b, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22057:
----------------------------------------
Yes, seems critical enough to try to fix it for the respin.
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, respin-b, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-628) JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-628?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-628.
------------------------------
Fix Version/s: 4.3.0.CR1
Resolution: Done
This was caused by bad arguments to my Jenkins job. The build p2director tests are blue - my error.
> JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions
> --------------------------------------------------------------------------------------------
>
> Key: JBTIS-628
> URL: https://issues.jboss.org/browse/JBTIS-628
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 4.3.0.CR1
>
> Attachments: 3-copies-of-comm.proj.examples_GA.png, 4-copies-of-comm.proj.examples_EA.png
>
>
> {quote}
> Might be nothing but the p2director install tests [1] failed on multiple org.jboss.tools.community.project.examples being defined:
> 16:55:46 INSTALL FAILED
> 16:55:46
> 16:55:46 [p2.dir] Installing tern-server-nodejs-feature.feature.group 1.1.0.201511082254.
> 16:55:46 [p2.dir] Cannot complete the install because of a conflicting dependency.
> 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples 3.0.1.CR1-v20160324-1911-B99 (org.jboss.tools.community.project.examples.feature.feature.group 3.0.1.CR1-v20160324-1911-B99)
> 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples Developer Resources 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples.feature.source.feature.group 3.0.1.Beta2-v20160121-2329-B74)
> 16:55:46 [p2.dir] Only one of the following can be installed at once:
> 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples 3.0.1.Beta2-v20160121-2329-B74)
> 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.0.Final-v20151001-1531-B45 (org.jboss.tools.community.project.examples 3.0.0.Final-v20151001-1531-B45)
> I'm pulling in version 3.0.1.CR1 here:
> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> --paull
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p...
> {quote}
> Reason for this failure is that you're pulling from TWO versions of JBT:
> * 3.0.1.Beta2-v20160121-2329-B74
> * 3.0.0.Final-v20151001-1531-B45
> You should only be pulling from ONE.
> Your composites have 3 or 4 different copies of the same features. And of those, there are 3 different VERSIONS. See screenshots. This is terribly wrong. You should only need to include a single version, and don't need to include 3-4 copies.
> Here are the URLs used by your install test job:
> http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s...
> http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22114) Server Adapter wizard: project selected via content assist is ignored
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22114?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22114:
------------------------------------------
[~fbricon] plz review and test my PR https://github.com/jbosstools/jbosstools-openshift/pull/1091
> Server Adapter wizard: project selected via content assist is ignored
> ---------------------------------------------------------------------
>
> Key: JBIDE-22114
> URL: https://issues.jboss.org/browse/JBIDE-22114
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift_v3, respin-b, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
>
> Say you have 2 webapp projects in the workspace.
> When you create an openshift server adapter, a default project is selected, if you switch to another project, by typing the project name,
> the source path is not updated. Even if you set the source path manually, the selected project is ignored when creating the project (as seen in the server editor).
> Using the browse button to select the project, then there is no problem
> # ASSERT: have 2+ projects in your workspace
> # ASSERT: have a running application in OpenShift
> # EXEC: launch server adapter wizard
> # EXEC: in wizard: open up "Advanced >>" so that you can see "Source Path:"
> # EXEC: in wizard: put curson into the text field for "Eclipse Project:", delete the preselected project and start typing to match your other workspace project (selecting it via "Browse" works flawlessley)
> # ASSERT: content assist pops up and suggests your other project
> # EXEC: select the suggested project
> Result:
> The source path is not updated
> in the Eclipse log you can find the following:
> {code}
> java.lang.IllegalArgumentException: Missing public setter method for deployProject property
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:52)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:54)
> at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:85)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:111)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:58)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111)
> at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:487)
> at org.eclipse.core.databinding.ValueBinding$3$1.run(ValueBinding.java:206)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:196)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:158)
> at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:147)
> at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:46)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
> at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
> at org.eclipse.jface.internal.databinding.swt.WidgetListener.handleEvent(WidgetListener.java:56)
> 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.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1334)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2591)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2517)
> at org.eclipse.jface.fieldassist.TextContentAdapter.setControlContents(TextContentAdapter.java:36)
> at org.eclipse.jface.fieldassist.ContentProposalAdapter.setControlContent(ContentProposalAdapter.java:1966)
> at org.eclipse.jface.fieldassist.ContentProposalAdapter.proposalAccepted(ContentProposalAdapter.java:1941)
> at org.eclipse.jface.fieldassist.ContentProposalAdapter.access$9(ContentProposalAdapter.java:1938)
> at org.eclipse.jface.fieldassist.ContentProposalAdapter$ContentProposalPopup.acceptCurrentProposal(ContentProposalAdapter.java:989)
> at org.eclipse.jface.fieldassist.ContentProposalAdapter$ContentProposalPopup.access$8(ContentProposalAdapter.java:982)
> at org.eclipse.jface.fieldassist.ContentProposalAdapter$ContentProposalPopup$TargetControlListener.handleEvent(ContentProposalAdapter.java:356)
> at org.eclipse.jface.fieldassist.ContentProposalAdapter$1.handleEvent(ContentProposalAdapter.java:1707)
> 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.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1365)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:763)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3325)
> at org.eclipse.swt.widgets.Text.gtk_key_press_event(Text.java:1814)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1980)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5685)
> at org.eclipse.swt.widgets.Text.windowProc(Text.java:2789)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4717)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9326)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1225)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2435)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> 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:483)
> 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