[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher refresh view but collapse tree items to project level
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Description: When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod in running state. Once watcher should update resources automatically, tree items are collapsed to project level (if service was visible, it is not anymore, only connection with its project). (was: When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.)
> OpenShift Explorer: Watcher refresh view but collapse tree items to project level
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod in running state. Once watcher should update resources automatically, tree items are collapsed to project level (if service was visible, it is not anymore, only connection with its project).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher refresh view but collapse tree items to project level
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Steps to Reproduce:
ASSERT: Have an OpenSHift 3 connection.
EXEC: Create new project for the connection.
EXEC: Open New OpenShift Application wizard, use existing connection, select e.g. eap 6.4. basic s2i template and proceed to create a new application.
ASSERT: There is a running Build pod under an EAP service in OpenShift Explorer view.
RESULT: Once the build pod is finished, view is refreshed but nodes are collapsed project level (only connection and project is visible)
EXPECTED RESULT: Once the build pod is finished, view is refreshed and tree items which had been visible and expanded would stay like that and service should reflect current state of pods on the server (= tree items should not be collapsed to project level).
was:
ASSERT: Have an OpenSHift 3 connection.
EXEC: Create new project for the connection.
EXEC: Open New OpenShift Application wizard, use existing connection, select e.g. eap 6.4. basic s2i template and proceed to create a new application.
ASSERT: There is a running Build pod under an EAP service in OpenShift Explorer view.
RESULT: The build pod is still there in running state OR once the build is finished (you can check it via oc binary or web ui), project is collapsed but upon expanding a project there is still only build pod in running state (although application pod is up and running on OpenShift server).
EXPECTED RESULT: Watcher updates view once a build is finished and shows application pod in its current state.
> OpenShift Explorer: Watcher refresh view but collapse tree items to project level
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher refresh view but collapse tree items to project level
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Summary: OpenShift Explorer: Watcher refresh view but collapse tree items to project level (was: OpenShift Explorer: Watcher does not work)
> OpenShift Explorer: Watcher refresh view but collapse tree items to project level
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher refresh view but collapse tree items to project level
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Priority: Major (was: Critical)
> OpenShift Explorer: Watcher refresh view but collapse tree items to project level
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22041) Exception is logged when I do not want to open cheatsheet
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22041?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-22041.
---------------------------------
Retested in version:
Version: 10.0.0.Alpha1
Build id: Alpha1-v20160429-1112-B5258
Build date: 20160429-1112
No error is shown in the error log.
> Exception is logged when I do not want to open cheatsheet
> ---------------------------------------------------------
>
> Key: JBIDE-22041
> URL: https://issues.jboss.org/browse/JBIDE-22041
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.1.CR1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.OperationCanceledException)
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433)
> 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:497)
> 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)
> Caused by: org.eclipse.core.runtime.OperationCanceledException
> at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.promptToShowCheatsheets(CheatSheetUtil.java:434)
> at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.access$1(CheatSheetUtil.java:394)
> at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil$1.run(CheatSheetUtil.java:378)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22361:
---------------------------------------
[~fbricon] asked me to investigate changing this particular line: https://github.com/jbosstools/jbosstools-openshift/pull/1144/files#diff-f... that was added. I think it's worth editing this issue to reflect the undesirable UI behavior
> OpenShift Explorer: Watcher does not work
> -----------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-708) Updated XML tests, XML model editor and dialogs
by stanislav kaleta (JIRA)
stanislav kaleta created JBTIS-708:
--------------------------------------
Summary: Updated XML tests, XML model editor and dialogs
Key: JBTIS-708
URL: https://issues.jboss.org/browse/JBTIS-708
Project: JBoss Tools Integration Stack
Issue Type: Enhancement
Components: QE, teiid
Affects Versions: 4.3.0.Beta1, 4.2.5.Final
Reporter: stanislav kaleta
Assignee: Andrej Podhradsky
Fix For: 4.2.6.Final, 4.3.0.Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22361:
---------------------------------------
Ok, I have tested it on latest available JBDS build v20160515-2224-B5363. The problem with not showing pods at current state is gone. What stayed is collapsing of nodes. Having a service expanded and waiting till there will be an application pod, the nodes are collapsed to project level. Changes to pod amount and their states performed via different channel than IDE are reflected correctly in IDE. Do you wanna create a new issue for that or are you gonna change this JIRA to be accurate with current state (collapsing of nodes)?
> OpenShift Explorer: Watcher does not work
> -----------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Once watcher should update resources automatically, service is collapsed, also project is collapsed, but after expanding those tree items, there is still old pod. Current pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3769:
-----------------------------------
Another benefit of removing jspm - reduction in startup time, see JBDS-3651.
> Remove JSPM from dependencies
> -----------------------------
>
> Key: JBDS-3769
> URL: https://issues.jboss.org/browse/JBDS-3769
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.0.Alpha3
>
>
> After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
> Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months