[JBoss JIRA] (JBIDE-21722) UX for "problem was found..." is unfortunate when there are mulitple errors and destinations
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21722?page=com.atlassian.jira.plugi... ]
Marcel Bruch commented on JBIDE-21722:
--------------------------------------
> 1) would be nice to add same comment to all (or at least when same event)
IMO this would be an unexpected behavior: comments may differ depending on who receives the error report. It would also not be transparent for a user that entering a comment to a single event would be copied into other reports as well.
If this should be implemented, we'd need to group events by their causing status (2-level tree "status"--> report-1, report-2).Then if a user comments on the root status object those comments can be copied into the children. But I'm not sure whether the additional level in the tree viewer would rather confuse users...
2) can't see who is requesting error reports besides the icon.
The "details " section names the endpoint. Which other locations do you have in mind? Multiline Text widgets (on Mac) do not support "setMessage". We could implement a pseudo message like "This report goes to XYZ" which will be shown as long as the user does not provide comments. Other suggestions?
> UX for "problem was found..." is unfortunate when there are mulitple errors and destinations
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-21722
> URL: https://issues.jboss.org/browse/JBIDE-21722
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aeri
> Reporter: Max Rydahl Andersen
> Attachments: A_Problem_Was_Found…_and_Java_EE_-_JBoss_Central_-_Eclipse.png
>
>
> Running Mars.2 with our jbosstools aeri discovery mechanism enabled and generating 4 errors in a row resulted in a dialog popping up with 8 events and its hard to see what user is meant to do and what he can do.
> A few issues:
> 1) comment field seem to be just for the selected event - would be nice to add same comment to all (or at least when same event)
> 2) can't see who is requesting error reports besides the icon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21723) debug/warning errors from aeri in logs
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21723?page=com.atlassian.jira.plugi... ]
Marcel Bruch commented on JBIDE-21723:
--------------------------------------
LocalReportsHistory.doRemember logs debug output:
https://git.eclipse.org/r/#/c/66984/
Unexpected response : UNKNOWN ‐ UNKNOWN:
Needs a minor adjustment on the Eclipse server side. Scheduled for next week.
> debug/warning errors from aeri in logs
> --------------------------------------
>
> Key: JBIDE-21723
> URL: https://issues.jboss.org/browse/JBIDE-21723
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri
> Reporter: Max Rydahl Andersen
>
> seeing a info and warning message when errors occurs.
> {code}
> eclipse.buildId=4.6.0.I20151209-2300
> java.version=1.8.0_20
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> org.eclipse.epp.logging.aeri.ide
> Info
> Fri Feb 19 18:56:42 CET 2016
> Added ‘Unknown category 'org.jboss.to…8.jar_5289305038018513896.jar’ under ‘b2c2e18436026b0d358c3d135c923fc4’ to local history at /Users/max/workspaces/eclipsee…org.jboss.tools/local-history. ; version: 1.100.0.v20160203-1727
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.doRemember(LocalReportsHistory.java:137)
> at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.remember(LocalReportsHistory.java:119)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:190)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69)
> at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> and
> {code}
> eclipse.buildId=4.6.0.I20151209-2300
> java.version=1.8.0_20
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> org.eclipse.epp.logging.aeri.ide
> Warning
> Fri Feb 19 18:56:42 CET 2016
> Unexpected response : UNKNOWN ‐ UNKNOWN ; version: 1.100.0.v20160203-1727
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.tryParse(IO.java:237)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.upload(IO.java:116)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:189)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69)
> at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20998) Application wizard: Validation error description in Resource Labels page is cut off
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-20998:
-----------------------------------------------
[~fbricon] please take a look at the pull request.
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20998
> URL: https://issues.jboss.org/browse/JBIDE-20998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21726) Test OpenShiftProjectCacheTest.testConnectionChanged() fails
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21726?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21726:
-----------------------------------------------
[~adietish] [~jcantrill] please take a look at the pull request.
> Test OpenShiftProjectCacheTest.testConnectionChanged() fails
> ------------------------------------------------------------
>
> Key: JBIDE-21726
> URL: https://issues.jboss.org/browse/JBIDE-21726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Fix For: 4.3.1.CR1
>
>
> 0. Connection is preset with one project.
> 1. Test fires project added. OpenShiftProjectCache processes that correctly.
> 2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0.
> 3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly.
> 4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2.
> Solution 1: for this test connection should return empty list of projects.
> Solution 2: start with connection that has 2 projects, and before firing events call cache.getProjectsFor(conn) - that will provide the initial loading projects into cache.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21726) Test OpenShiftProjectCacheTest.testConnectionChanged() fails
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21726?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-21726:
------------------------------------------
Description:
0. Connection is preset with one project.
1. Test fires project added. OpenShiftProjectCache processes that correctly.
2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0.
3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly.
4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2.
Solution 1: for this test connection should return empty list of projects.
Solution 2: start with connection that has 2 projects, and before firing events call cache.getProjectsFor(conn) - that will provide the initial loading projects into cache.
was:
0. Connection is preset with one project.
1. Test fires project added. OpenShiftProjectCache processes that correctly.
2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0.
3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly.
4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2.
Solution: for this test connection should return empty list of projects.
> Test OpenShiftProjectCacheTest.testConnectionChanged() fails
> ------------------------------------------------------------
>
> Key: JBIDE-21726
> URL: https://issues.jboss.org/browse/JBIDE-21726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Fix For: 4.3.1.CR1
>
>
> 0. Connection is preset with one project.
> 1. Test fires project added. OpenShiftProjectCache processes that correctly.
> 2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0.
> 3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly.
> 4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2.
> Solution 1: for this test connection should return empty list of projects.
> Solution 2: start with connection that has 2 projects, and before firing events call cache.getProjectsFor(conn) - that will provide the initial loading projects into cache.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21726) Test OpenShiftProjectCacheTest.testConnectionChanged() fails
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-21726:
---------------------------------------------
Summary: Test OpenShiftProjectCacheTest.testConnectionChanged() fails
Key: JBIDE-21726
URL: https://issues.jboss.org/browse/JBIDE-21726
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Viacheslav Kabanovich
Fix For: 4.3.1.CR1
0. Connection is preset with one project.
1. Test fires project added. OpenShiftProjectCache processes that correctly.
2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0.
3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly.
4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2.
Solution: for this test connection should return empty list of projects.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21719:
-----------------------------------------------
Layout of JBoss perspective is done so that the border between bottom-central and bottom-rigth parts can be moved left and right independently of the top-right part. The initial width of bottom-rigth part does not have to be as small as that of the top-right part. We can reach a compromise in which proportion to divide the bottom between its central and right parts at the initialization of the perspective. And different initial widths of top-right and bottom-right will let user guess that he can easily adjust that proportion. For example
!JBossPerspective_PropertiesMayBeWider.png!
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-21719:
------------------------------------------
Attachment: JBossPerspective_PropertiesMayBeWider.png
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-68) Rename Chome Developer Tools features and include them into main JSDT Debug feature [EBZ#486504]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-68?page=com.atlassian.jira.plugin.sys... ]
Victor Rubezhny edited comment on ERT-68 at 2/19/16 5:28 PM:
-------------------------------------------------------------
[~dgolovin] Why do you closed the issue? Shouldn't we add ChDT features into WTP p2 repo?
was (Author: vrubezhny):
[~dgolovin] Why did you closed the issue? Shouldn't we add ChDT features into WTP p2 repo?
> Rename Chome Developer Tools features and include them into main JSDT Debug feature [EBZ#486504]
> ------------------------------------------------------------------------------------------------
>
> Key: ERT-68
> URL: https://issues.jboss.org/browse/ERT-68
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Denis Golovin
> Labels: 3.8_M6, Debug, bzira
> Fix For: Neon (4.6) M6
>
>
> We need to rename ChDT features (according to the JSDT ones) and to include them into the main JSDT Debug Features in order to include ChDT into the overal WTP build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month