Community
Participate
Working Groups
See bug#154090 for details on this new api and http://wiki.eclipse.org/index.php/Status_Handling_Best_Practices.
Docs on using the new API: http://wiki.eclipse.org/index.php/Status_Handling_Best_Practices
Even if we don't get to using the new API, we should still make sure that we start passing the plug-in ID or a proper status to the MylarStatusHandler (and rename that class). Currently when connectors use that the error log provides no indication of where the error is from. Rob: marking P1 since we need to get to it this week.
*** Bug 191774 has been marked as a duplicate of this bug. ***
In order to keep 3.2 compatibility we are now using our own StatusHandler class which will be straightforward to port to Platform's StatusManager once we are able to break 3.2 backwards compatibility for this.
It is currently unclear to me if there is any benefit in switching to the platform status handler. Some of our status handling requires custom UI, e.g. for displaying HTML errors, which is currently not supported by the platform handler.
Agreed, unfortunately. Let's hold off for now.
What exactly do you need from statushandling?
I'll review the StatusHandler API again to determine if we can use it as a replacement for our own error handling mechanism.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn