[JBoss JIRA] (JBIDE-21467) Quick access 'open via livereload' with stopped application server is misbehaving
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi... ]
Jan Richter commented on JBIDE-21467:
-------------------------------------
I just selected the server module, used ctrl+3 for quick access, chose the livereload option and pressed enter. I've also attached the message screenshot.
> 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 Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-21467:
--------------------------------
Attachment: livereload.png
> 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:
---------------------------------------
[~jrichter1],
There's something I cannot reproduce when reading the issue description: if the server is stopped, the "Open with LiveReload" command on the server module (eg, a sample application deployed on WildFly) is disabled. So how can you invoke it. Also, can you clarify when/how you have the 'Unable to open module ...' message ?
> 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
>
> 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 reassigned JBIDE-21467:
-------------------------------------
Assignee: Xavier Coulon
> 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
>
> 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 Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-21467:
--------------------------------
Description:
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}
was:
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. And it won't even try to open anything in the browser.
> 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
>
> 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 Jan Richter (JIRA)
Jan Richter created JBIDE-21467:
-----------------------------------
Summary: 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
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. And it won't even try to open anything in the browser.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21466) Don't scroll up the software/update list when Enable EA dialog is cancelled
by Jan Richter (JIRA)
Jan Richter created JBIDE-21466:
-----------------------------------
Summary: Don't scroll up the software/update list when Enable EA dialog is cancelled
Key: JBIDE-21466
URL: https://issues.jboss.org/browse/JBIDE-21466
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: central
Affects Versions: 4.3.1.Beta2
Reporter: Jan Richter
Priority: Optional
Central -> software/update -> enable early access -> dialog opens.
Now when the dialog is closed, the software list is refreshed and scrolls to the top. Can it stop doing that when the dialog is cancelled or closed otherwise than with the 'Yes' button? Nothing changes if I don't say yes, so there is no point in refreshing the list, right?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21465) 'Disable some filters' option behaves strangely with 'Show installed'
by Jan Richter (JIRA)
Jan Richter created JBIDE-21465:
-----------------------------------
Summary: 'Disable some filters' option behaves strangely with 'Show installed'
Key: JBIDE-21465
URL: https://issues.jboss.org/browse/JBIDE-21465
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.3.1.Beta2
Reporter: Jan Richter
Priority: Minor
Attachments: filter.png, installed.png
I've installed everything from central software/update -> now it says there is nothing to install and gives me an option to disable some filters. Clicking that produces the following dialog:
!filter.png|thumbnail!
The first strange part is, I actually need to uncheck the 'Show installed' checkbox in this dialog to show the installed plugins. It might be technically disabling the filter, but it looks weird.
The second strange thing is, after 'disabling the filter' it shows the installed plugins, but the 'Show installed' checkbox is still unchecked.
!installed.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months