Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Error Reporting Tool Improvement


I would certainly like to echo your call for more wide spread use of the error reporting tools by all projects.  There is a wealth of information here.  The fact that you're very responsive to improvements is also a huge win for the committer community. 

Thanks so much!


On 06/05/2015 9:48 PM, Marcel Bruch wrote:
Hello cross-projects,

On 06 May 2015, at 13:54, Ed Merks <Ed.Merks@xxxxxxxxx> wrote:

I would like to suggest that the "blame" logic should consider that Display.readAndDispatch processes events of arbitrary origin.

I spent some time analyzing how large the effect of such a change would be. I judged all differences between the current mappings and the new ones and have to say that in many cases this works better than the old approach. The results can be viewed live. Further suggestions are welcome. Please use bug 466576 [1] for that.

Kudos for creating this great technology!

Maybe this is a good moment to ask committers on cross-projects to leverage the error reporting in their projects as well. Major projects like JDT, JSDT, Xtext, and EGit make good use of it and even large projects like JDT get around 3-5 error reports per day to look at. In the last two weeks more than 70 automated problem reports could been fixed and even external contributors start chasing bugs to help making Eclipse Mars great (e.g. [2]).

Please contact me if you want to set-up email digests or automated reports to bugzilla for your project. I’m happy to help setting it up.


cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top