Re: [cross-project-issues-dev] Error reporter and third-party code

[Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>]

Am 24.07.2015 um 19:55 schrieb Max Rydahl Andersen <manderse@xxxxxxxxxx>:

On 24 Jul 2015, at 17:27, Marcel Bruch wrote:

I think those clients (which currently make ~28% of the error reports) should actually sign-up and subscribe to their error reports

How do I subscribe to error reports that are filtered ?

Support for this is limited. Check the Saphire alert [1] which listens to problems marked as „THIRD“. Note that the global filtering rules still apply (logged by an org.eclipse plugin, 3rd party class names likely anonymized).

- or set up their own error collection to review and fix their issues themselves.

...adding another layer of error reporting will give even worse end-user experience imo - i.e. how do I know that eclipse error reporter haven't reported it ?

A matter of implementation. There could be one listener that inspects the log event and delivers it different endpoints based on some criteria - or to the same endpoint (e.g eclipse.org if Eclipse would start collecting error reports for, say, its member companies - and for their commercial products / non-eclipse.org plugins?).

Marcel

[1] https://dev.eclipse.org/recommenders/committers/confess/#/projects/54d39c63e4b0d2e72753bc99

-- 

Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt

Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940