[JBoss JIRA] (JBIDE-21470) Use MessageDialog instead of MessageBox in ZombieProcessPrompter
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-21470:
----------------------------------
Summary: Use MessageDialog instead of MessageBox in ZombieProcessPrompter
Key: JBIDE-21470
URL: https://issues.jboss.org/browse/JBIDE-21470
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.3.1.Beta1
Reporter: Radim Hopp
Priority: Minor
Our integration tests sometimes get stuck on this MessageBox as it creates native window which RedDeer nor SWTBot can access. Using MessageDialog enable us to handle it within our integration tests and as a bonus it matches eclipse look&feel better (imo).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21469) Quick access 'open via livereload' with stopped application server is misbehaving
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21469?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21469:
----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-livereload/pull/120 (was: https://github.com/jbosstools/jbosstools-livereload/pull/119)
> Quick access 'open via livereload' with stopped application server is misbehaving
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21469
> URL: https://issues.jboss.org/browse/JBIDE-21469
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.
> If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.
> It does however add this entry to the error log:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.SWT.error(SWT.java:4377)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21469) Quick access 'open via livereload' with stopped application server is misbehaving
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21469:
-------------------------------------
Summary: Quick access 'open via livereload' with stopped application server is misbehaving
Key: JBIDE-21469
URL: https://issues.jboss.org/browse/JBIDE-21469
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload
Affects Versions: 4.3.1.Beta2
Reporter: Jan Richter
Assignee: Xavier Coulon
Fix For: 4.3.1.Beta2
Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.
If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.
It does however add this entry to the error log:
{noformat}
Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:4491)
at org.eclipse.swt.SWT.error(SWT.java:4406)
at org.eclipse.swt.SWT.error(SWT.java:4377)
at org.eclipse.swt.widgets.Display.error(Display.java:1186)
at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21469) Quick access 'open via livereload' with stopped application server is misbehaving
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21469?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21469:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta2)
> Quick access 'open via livereload' with stopped application server is misbehaving
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21469
> URL: https://issues.jboss.org/browse/JBIDE-21469
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.
> If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.
> It does however add this entry to the error log:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.SWT.error(SWT.java:4377)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21467) Quick access 'open via livereload' with stopped application server is misbehaving
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21467:
----------------------------------
Fix Version/s: 4.3.1.Beta2
> Quick access 'open via livereload' with stopped application server is misbehaving
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21467
> URL: https://issues.jboss.org/browse/JBIDE-21467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.3.1.Beta2
>
> Attachments: livereload.png
>
>
> Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.
> If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.
> It does however add this entry to the error log:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.SWT.error(SWT.java:4377)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21467) Quick access 'open via livereload' with stopped application server is misbehaving
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21467:
---------------------------------------
Looks like Eclipse behaves slightly differently on Linux (assuming you're running on Linux) compared to MacOSX, because on the latter, the error dialog did not appear at all.
> Quick access 'open via livereload' with stopped application server is misbehaving
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21467
> URL: https://issues.jboss.org/browse/JBIDE-21467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Attachments: livereload.png
>
>
> Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.
> If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.
> It does however add this entry to the error log:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.SWT.error(SWT.java:4377)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21467) Quick access 'open via livereload' with stopped application server is misbehaving
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21467:
---------------------------------------
ok, I see the exception, but I can't get the error message that you reported because the LiveReload tooling offers me to create a LiveReload server on-the-fly.
I'll fix this {{Invalid Thread Access}} issue but I'm still curious to see how you got this message 'Unable to open module ...'. Here, with WildFly started, I got the dialog to create/start the LiveReload server in both case: LiveReload server did not exist or was stopped.
> Quick access 'open via livereload' with stopped application server is misbehaving
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21467
> URL: https://issues.jboss.org/browse/JBIDE-21467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Attachments: livereload.png
>
>
> Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.
> If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.
> It does however add this entry to the error log:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.SWT.error(SWT.java:4377)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months