[JBoss JIRA] (JBIDE-24780) Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-24780:
--------------------------------------
Summary: Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)
Key: JBIDE-24780
URL: https://issues.jboss.org/browse/JBIDE-24780
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Mickael Istria
I've created an OpenShift Application from Eclipse IDE providing it an Eclipse Project as input.
Then I tried to create a server adapter for this project. It didn't work initially because the project isn't a Faceted Web project. I had to quit the OpenShift wizard, make the project a faceted one and restart the wizard.
I would expect the wizard to create a server adapter to suggest and link to a way to make the project associated with the application a web project in Eclipse IDE so it's one less step to understand for users before it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24774) ClassCastException while creating new Openshift connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24774?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24774:
------------------------------------------
When fixining this in a minimal way (https://github.com/jbosstools/jbosstools-openshift/pull/1533) - which allows me to verify JBIDE-24768 - I dont see extended properties being saved as it is expected.
> ClassCastException while creating new Openshift connection
> ----------------------------------------------------------
>
> Key: JBIDE-24774
> URL: https://issues.jboss.org/browse/JBIDE-24774
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Dmitrii Bocharov
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.0.Final
>
> Attachments: screencast.webm
>
>
> {code:java}
> java.lang.RuntimeException: java.lang.ClassCastException: org.jboss.tools.openshift.common.core.connection.NewConnectionMarker cannot be cast to org.jboss.tools.openshift.core.connection.Connection
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:102)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doGetValue(BeanValueProperty.java:49)
> at org.eclipse.core.databinding.property.value.ValueProperty.getValue(ValueProperty.java:62)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:121)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doGetValue(SimplePropertyObservableValue.java:102)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.getValue(AbstractObservableValue.java:88)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.getValue(DecoratingObservableValue.java:109)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.getValue(DecoratingObservableValue.java:109)
> at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:169)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:149)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:153)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:171)
> at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:162)
> at org.eclipse.core.databinding.ValueBinding.updateModelToTarget(ValueBinding.java:127)
> at org.eclipse.core.databinding.DataBindingContext.updateTargets(DataBindingContext.java:464)
> at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:216)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.connect(ConnectionWizardPage.java:385)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.performFinish(ConnectionWizard.java:77)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:778)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:417)
> at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:619)
> at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5252)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$2.widgetSelected(OpenShiftExplorerView.java:140)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5252)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1374)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1488)
> at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:384)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1956)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:6168)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5512)
> 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:9251)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1252)
> 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:2110)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4105)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.refle
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24768) openshift connection wizard advanced section persists changes when canceled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24768?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24768 at 7/31/17 11:25 AM:
--------------------------------------------------------------------
[~rob.stryker] [~mmalina] [~rhopp] after the patch, cancel indeed wont save the changes. But "Finish" wont save them either (for me).
was (Author: adietish):
[~rob.stryker] [~mmalina] cancel indeed wont save the changes, but "Finish" wont save them either (for me).
> openshift connection wizard advanced section persists changes when canceled
> ---------------------------------------------------------------------------
>
> Key: JBIDE-24768
> URL: https://issues.jboss.org/browse/JBIDE-24768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.Final
>
>
> When you have an openshift connection, if you right-click on it and edit it, you can then change it's properties. If you expand the advanced section, and make changes, and then cancel the wizard, all changes are persisted when they should not be.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24768) openshift connection wizard advanced section persists changes when canceled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24768?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24768 at 7/31/17 11:25 AM:
--------------------------------------------------------------------
[~rob.stryker] [~rhopp] after the patch, cancel indeed wont save the changes. But "Finish" wont save them either (for me).
was (Author: adietish):
[~rob.stryker] [~mmalina] [~rhopp] after the patch, cancel indeed wont save the changes. But "Finish" wont save them either (for me).
> openshift connection wizard advanced section persists changes when canceled
> ---------------------------------------------------------------------------
>
> Key: JBIDE-24768
> URL: https://issues.jboss.org/browse/JBIDE-24768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.Final
>
>
> When you have an openshift connection, if you right-click on it and edit it, you can then change it's properties. If you expand the advanced section, and make changes, and then cancel the wizard, all changes are persisted when they should not be.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24768) openshift connection wizard advanced section persists changes when canceled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24768?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24768:
------------------------------------------
[~rob.stryker] [~mmalina] cancel indeed wont save the changes, but "Finish" wont save them either (for me).
> openshift connection wizard advanced section persists changes when canceled
> ---------------------------------------------------------------------------
>
> Key: JBIDE-24768
> URL: https://issues.jboss.org/browse/JBIDE-24768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.Final
>
>
> When you have an openshift connection, if you right-click on it and edit it, you can then change it's properties. If you expand the advanced section, and make changes, and then cancel the wizard, all changes are persisted when they should not be.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24779) Starting an OpenShift application seems to lock workspace
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-24779:
--------------------------------------
Summary: Starting an OpenShift application seems to lock workspace
Key: JBIDE-24779
URL: https://issues.jboss.org/browse/JBIDE-24779
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Mickael Istria
I have an openshift application starting from the IDE and can see the progress report. For some reason (not IDE related I imagine), it's taking ages.
In the meantimes, I've tried to turn a regular project into a static web project to be able to create a server adapter, but it seems like the OpenShift Start operation is locking the workspace so my change show a "waiting for background job to complete pop-up", which is persisting as the job in the background doesn't complete.
I have the impression that the openshift start job does lock the workspace and prevents many things from being doable. If it's the case, I believe it should be changed to a regular job without any lock so it's not blocking the user.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24675) install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24675?page=com.atlassian.jira.plugi... ]
Lukáš Valach commented on JBIDE-24675:
--------------------------------------
[~nickboldt], since we are on Eclipse 4.5 plugins are installed on background and shell 'Installing Software' (window with progress bar) is not displayed.
I propose to apply this PR \[1\], but we also need to rebuild \[2\] and upload new build to nexus. I guess that it could be done using this job \[3\].
\[1\] https://github.com/jbosstools/jbosstools-install-grinder/pull/35
\[2\] https://github.com/jbosstools/jbosstools-install-grinder
\[3\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Should I also increase build number? (4.5.0-SNAPSHOT -> 4.5.1-SNAPSHOT ?)
> install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24675
> URL: https://issues.jboss.org/browse/JBIDE-24675
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: install-tests
> Affects Versions: 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 4.5.0.Final
>
>
> {code}
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0040f (Add Reposi)
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:38 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:38 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:56 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0008e (workspace )
> 15:51:56 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:52:02 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.816 sec
> 15:52:02
> 15:52:02 Testcase: testInstall took 26.254 sec
> 15:52:02 Caused an ERROR
> 15:52:02 Internal error
> 15:52:02 java.lang.RuntimeException: Internal error
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:213)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:147)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.installFromSite(InstallTest.java:133)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.testInstall(InstallTest.java:78)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.internal.CapturingFrameworkMethod.invokeExplosively(CapturingFrameworkMethod.java:47)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBothttps://dev-platform-jenkins.rh...
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:60)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:120)
> 15:52:02 at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:73)
> 15:52:02 at java.lang.Thread.run(Thread.java:748)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:472)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntilWidgetAppears(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shells(SWTBotFactory.java:116)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shells(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:106)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:97)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:156)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 5000 ms.: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:522)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:496)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:484)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:466){code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24774) ClassCastException while creating new Openshift connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24774?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24774:
-------------------------------------
Comment: was deleted
(was: There's more broken here. Now one cannot change any setting and try again. You have to close the wizard and try again. Before you could simply change url, user/pw or token to have the error go away so that "Finish" gets enabled again and you can have another try. Currently changing any setting has no effect, the error stays and "Finish" (therefore) stays disabled.
)
> ClassCastException while creating new Openshift connection
> ----------------------------------------------------------
>
> Key: JBIDE-24774
> URL: https://issues.jboss.org/browse/JBIDE-24774
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Dmitrii Bocharov
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.0.Final
>
> Attachments: screencast.webm
>
>
> {code:java}
> java.lang.RuntimeException: java.lang.ClassCastException: org.jboss.tools.openshift.common.core.connection.NewConnectionMarker cannot be cast to org.jboss.tools.openshift.core.connection.Connection
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.readProperty(BeanPropertyHelper.java:102)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doGetValue(BeanValueProperty.java:49)
> at org.eclipse.core.databinding.property.value.ValueProperty.getValue(ValueProperty.java:62)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:121)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doGetValue(SimplePropertyObservableValue.java:102)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.getValue(AbstractObservableValue.java:88)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.getValue(DecoratingObservableValue.java:109)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.getValue(DecoratingObservableValue.java:109)
> at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:169)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:149)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:153)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:171)
> at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:162)
> at org.eclipse.core.databinding.ValueBinding.updateModelToTarget(ValueBinding.java:127)
> at org.eclipse.core.databinding.DataBindingContext.updateTargets(DataBindingContext.java:464)
> at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:216)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.connect(ConnectionWizardPage.java:385)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizard.performFinish(ConnectionWizard.java:77)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:778)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:417)
> at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:619)
> at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5252)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$2.widgetSelected(OpenShiftExplorerView.java:140)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5252)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1374)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1488)
> at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:384)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1956)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:6168)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5512)
> 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:9251)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1252)
> 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:2110)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4105)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.refle
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24758) Server editor complains about wrong runtime folder even if fixed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24758?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24758:
-------------------------------------
I'm able to replicate the first half (UI warning, doesn't go away), but I'm unable to replicate the part about the server actually not starting.
What if you delete the classpath entry from the launch configuration, save, and try again?
> Server editor complains about wrong runtime folder even if fixed
> ----------------------------------------------------------------
>
> Key: JBIDE-24758
> URL: https://issues.jboss.org/browse/JBIDE-24758
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
>
> I had a runtime and server adapter set up for eap 6.4. I deleted the server on the disk. When I opened the server editor, I was shown a red message in the status bar:
> The server's runtime folder does not exist: ......
> So far so good.
> So I unzip eap 6.4 somewhere else, clicked Runtime Environment in the server editor, and pointed the runtime to the new correct directory. Then I saved the editor. But the error message in the status bar still won't go away. I have to close the editor and then open it again, then the message no longer shows up.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months