Community
Participate
Working Groups
We should consider enhancing our error reporting to take advantage of the fact that e4 can display views in dialogs. At least one of our failure cases results in a dialog that explicitly says to 'Open the Error view for details' while others result in an 'Internal Error' dialog being opened. In both of these cases there is more info in the Error View than is available from the dialog itself...
M2 is done...
At least we know we can do this now since I've demo'd it in a webinar...;-).
Moving to M6, this is polish.
This would be nice but we'll do it in 4.3...
I've a very mixed feelings about this one. Status/Error Dialog was meant to provide human readable error messages that would not scary regular RCP users. Showing full error stack trace to non-IT user will make them running away.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.
