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 automatically to the error report as "auxiliary information” (requires user consent).

Besides the classpath analyzer we have a few more "common processors” in mind which allow users to easily 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. 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 with one click. Reviewers can also demand auxiliary information by setting the appropriate needinfo flags on the problem:

 

The exact API is not yet settled but I’d like to let you know early in the process to gather your requirements. In case 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

_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev