[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22057.
---------------------------------
Verified in JBDS 9.1.0.GA build B495.
> 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: Rob Stryker
> 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] (JBDS-3786) CDK fails on 'vagrant plugin install'
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3786?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3786:
-----------------------------
> CDK fails on 'vagrant plugin install'
> -------------------------------------
>
> Key: JBDS-3786
> URL: https://issues.jboss.org/browse/JBDS-3786
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
>
> Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fails on vagrant plugin installation. This is the error from install.log:
> {noformat}
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
> }
> }
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3786) CDK fails on 'vagrant plugin install'
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3786?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3786:
--------------------------------
> CDK fails on 'vagrant plugin install'
> -------------------------------------
>
> Key: JBDS-3786
> URL: https://issues.jboss.org/browse/JBDS-3786
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
>
> Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fails on vagrant plugin installation. This is the error from install.log:
> {noformat}
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
> }
> }
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3786) CDK fails on 'vagrant plugin install'
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3786?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3786:
--------------------------------
Status: New (was: New)
Target Release: 9.1.0.GA
> CDK fails on 'vagrant plugin install'
> -------------------------------------
>
> Key: JBDS-3786
> URL: https://issues.jboss.org/browse/JBDS-3786
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
>
> Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fails on vagrant plugin installation. This is the error from install.log:
> {noformat}
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
> }
> }
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-21857:
--------------------------------------
The PoC from Rob (calling GC via a JMX connection) works for me with the IBM JDK and a patched version of the JDK (the patch being for https://bugs.openjdk.java.net/browse/JDK-8153925, which totally borks full deployment).
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22151) Failed to install JBT in Eclipse
by Chunyun Chen (JIRA)
Chunyun Chen created JBIDE-22151:
------------------------------------
Summary: Failed to install JBT in Eclipse
Key: JBIDE-22151
URL: https://issues.jboss.org/browse/JBIDE-22151
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha1
Environment: Operating System: have tried Fedora 17 and 22
jbt version: 3.2.0.Alpha1-v20160409-1043-B1241
eclipse:
Version: Neon Milestone 6 (4.6.0M6)
Build id: 20160329-0659
Reporter: Chunyun Chen
Attachments: jbt_installation_1.png, jbt_installation_2.png
Will meet below dependency errors when installing jbt in eclipse:
"
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
Missing requirement: Openshift 3 Client 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.client 3.2.0.Alpha1-v20160409-1043-B1241) requires 'bundle org.eclipse.jetty.websocket.client 9.2.13' but it could not be found
Cannot satisfy dependency:
From: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
To: org.jboss.tools.openshift.client [3.2.0.Alpha1-v20160409-1043-B1241]
"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-22148:
---------------------------------------------
the update-site-jboss is back online. lets revert the fix, [~nickboldt] I created https://github.com/jbosstools/jbosstools-discovery/pull/331
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
> Affected jobs:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22148) Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
by Anton Arhipov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22148?page=com.atlassian.jira.plugi... ]
Anton Arhipov edited comment on JBIDE-22148 at 4/11/16 5:12 AM:
----------------------------------------------------------------
[~maxandersen] apparently it was a bug on our side. The update site is back.
was (Author: arhan):
[~maxandersen] the dedicated update site was introduced solely for tracking JRebel plugin download counts via JBoss DevStudio. I'm not sure what happened to it, but you could switch to the general update site, the one that is linked from Eclipse Marketplace
> Zeroturnaround JRebel update site no longer exists; automated Central install broken for 4 current versions of Central
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22148
> URL: https://issues.jboss.org/browse/JBIDE-22148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite, upstream
> Affects Versions: 4.1.2.Final, 4.2.3.Final, 4.3.0.Final, 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
>
> {code}
> 09:26:43 [p2.dir] !ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2016-04-09 09:26:43.985
> 09:26:43 [p2.dir] !MESSAGE No repository found at http://update.zeroturnaround.com/update-site-jboss/.
> {code}
> So, we need to use an alternate update site, such as the one linked from Eclipse Marketplace, eg., http://update.zeroturnaround.com/update-site/
> And we need to verify that the features we include in Central are still available on the new site.
> Affected jobs:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
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 Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22114?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22114.
---------------------------------
Verified in JBDS 9.1.0.GA build B495.
> 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