[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3566: ---------------------------------- "why are you creating your custom devstudio.redhat.com error discovery ?" Because nothing was working in JBDS, so I went back into this JIRA to see the latest comments from you, Max, about how to set something up: {quote}This jira is just about adding aeri to JBDS - not about setting up any servers etc. It would be great if you can test it works so "acceptedProducts" seem to be the right place to change that. How about downloading https://dev.eclipse.org/recommenders/community/confess/v2/discovery and change that part and let it include com.jbds.* and see if the UI flow actually works ?{quote} -- https://issues.jboss.org/browse/JBDS-3566?focusedCommentId=13156570&p... If it's working as expected in both JBDS 9.1 and 10.0, please provide steps to reproduce, because I couldn't get error reporting to fire for any of the errors I generated in either version of JBDS. And if you look at my screenshot on JBDS-3600 ( https://issues.jboss.org/secure/attachment/12399019/aeri-in-jbds10.png ) you'll see there's not even a JBoss Tools AERI reporting flavour there. The second reporting server only appears for JBDS 9.1 ( https://issues.jboss.org/secure/attachment/12399018/aeri-in-jbds91.png ) So, OK, maybe this *is* working, as you say... but I can't verify that so I'd love to know what you did to make it magically work OOTB in JBDS 9.1 or 10.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)