[ https://issues.jboss.org/browse/JBDS-3600?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3600: ---------------------------------- OK, so I've learned two things here: a) org.eclipse.recommenders.stacktraces.rcp.serverUrl should not be used (that was previously recommended in JBDS-3566, via links to documentation on https://wiki.eclipse.org/EPP/Logging#How_can_I_include_AERI_in_my_own_pro... ). If that's no longer true, that wiki should be updated. b) there is nowhere in JBDS where we use the *org.eclipse.epp.logging.aeri.ide.servers* extension point. All we ever did was to add this feature into our product definition: {code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.jboss.devstudio.core.product#L65} 63 <feature id="com.jboss.devstudio.core.capabilities.feature"/> 64+ <!-- JBDS-3566 new for Mars.2 / Neon.M4 --> 65+ <feature id="org.eclipse.epp.logging.aeri.feature"/> 66 </features> {code} I can certainly enable the extension point and set up our own JBDS-branded reporting server (red ball for JBDS instead of blue wrench for JBT). Is that something we want to do? I presume that's blocked by https://bugs.eclipse.org/bugs/show_bug.cgi?id=489484 -- This message was sent by Atlassian JIRA (v6.4.11#64026)