[jbosstools-dev] [aeri] Introducing (Custom) Error Report Processors

Dear jbosstools-dev, the next version of AERI will allow to run client-side analyses before an error report is send. For example, when a ClassNotFoundException is logged, AERI will run an analyzer that tries to parse the class name from the exception’s error message, search for all bundles that export that class (i.e., the containing package) and check which bundles and packages the failing bundle was wired to. The results of these analyses are added to the error report as "auxiliary information” automatically (requires user consent). Besides the classpath analyzer AERI will provide a few more "common processors” that allow users to add all system properties, all user preferences, all installed bundles, resolution status, and wiring information, all installed features + bundles with id, name, and version information, to an error report on demand. We may also take this a step further to allow users to attach screenshots or code snippets to an error report. The analyzers will be added to the review dialog as outlined below and can be de/activated in one click. Reviewers can also demand auxiliary information which will then be automatically added to the report (after user consent): Every project will be able to register their own client-side analyses via an extension point. The exact details are not yet settled but I’d like to let you know early in the process to gather your requirements. If you have a requirement or feature request, please let me/us know in bug 496656 [1]. Thank you, Marcel [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=496656 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=496656> -- 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/ <http://www.codetrails.com/> Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940