[JBoss JIRA] (JBIDE-21517) Disable livereload quick access option for modules on stopped server
by Jan Richter (JIRA)
Jan Richter created JBIDE-21517:
-----------------------------------
Summary: Disable livereload quick access option for modules on stopped server
Key: JBIDE-21517
URL: https://issues.jboss.org/browse/JBIDE-21517
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: livereload
Affects Versions: 4.3.1.Beta2
Reporter: Jan Richter
Since the 'show in web browser via livereload' quick access will fail in the end. Plus context menu option on modules is already disabled when the server is not running. It might be nicer to have both options disabled in this instance.
--
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 commented on JBIDE-21467:
-------------------------------------
Ok, new issue incoming: JBIDE-21517
> 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-21412) Allow for any adaptable to IServerModule to be opened via LiveReload
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21412?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21412.
-------------------------------
Verified in 4.3.1.Beta2 with LiveReload 1.3.1.Beta2-B69.
> Allow for any adaptable to IServerModule to be opened via LiveReload
> --------------------------------------------------------------------
>
> Key: JBIDE-21412
> URL: https://issues.jboss.org/browse/JBIDE-21412
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: livereload
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.Beta2
>
>
> The "Open in Web Browser via LiveReload" is only available if the selection is an `IServerModule` but this could be extended to any type of element that can be adapted to an `IServerModule, to provide more flexibility to other tools such as OpenShift where the server adapter is used as the target (ie, there is no server module for the deployed application)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21495) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21495?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-21495:
-------------------------------------
Assignee: Pavol Srna
[~psrna], please create the Beta2x branch. This should be all for us.
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
> ---------------------------------------------------------------
>
> Key: JBIDE-21495
> URL: https://issues.jboss.org/browse/JBIDE-21495
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Integration Tests]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta2x
> git push origin jbosstools-4.3.1.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.CR1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
> * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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:
---------------------------------------
I would need to further investigate for that. Can we put this in another issue ?
> 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-21430) Tab properties for Openshift Projects
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21430?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21430.
---------------------------------
Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154.
> Tab properties for Openshift Projects
> -------------------------------------
>
> Key: JBIDE-21430
> URL: https://issues.jboss.org/browse/JBIDE-21430
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: openshift_deployment_view
> Fix For: 4.3.1.Beta2
>
>
> Add tabbed properties for project where they content includes all the resource for a given project. This should provide a similiar visual display to what you would see in the OpenShift web console
--
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 commented on JBIDE-21467:
-------------------------------------
After the fix it no longer fails silently - it starts up a livereload server and then gives me the error from the screenshot. That's an improvement, but wouldn't it be simpler to just disable the quick access option in this instance, as it is in the context menu?
> 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-21504) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Forge]
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21504?page=com.atlassian.jira.plugi... ]
George Gastaldi closed JBIDE-21504.
-----------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Forge]
> ---------------------------------------------------
>
> Key: JBIDE-21504
> URL: https://issues.jboss.org/browse/JBIDE-21504
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Forge]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta2x
> git push origin jbosstools-4.3.1.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.CR1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
> * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21415) Incorrect content for property tabs
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21415?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21415:
---------------------------------------
Could you please describe what the issue was so I would be able to verify it. Because you are pointing to your personal project so I don't know what's the catch.
> Incorrect content for property tabs
> -----------------------------------
>
> Key: JBIDE-21415
> URL: https://issues.jboss.org/browse/JBIDE-21415
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: openshift_deployment_view
> Fix For: 4.3.1.Beta2
>
>
> The kibana service for https://10.3.9.15.xip.io:8443/console/project/logging/overview does not match the image stream tab impl for eclipse. I would expect logging kibana to reflect only the imagestreams:
> * for the authproxy
> * for kibana
> similiar for logging-es i would expect imagestream only fo
> *es
> and for fluentd only
> * fluentd
> This is similiar for all property tabs
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months