[ https://issues.jboss.org/browse/JBDS-3600?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3600 at 3/11/16 6:06 PM: ----------------------------------------------------------- I can't make Aeri work in JBDS 10.0.0.Alpha1. I've created a dummy aeri-discovery site here: https://devstudio.jboss.com/10.0/aeri-discovery/ I've tried installation of jboss-devstudio-10.0.0.Alpha1-v20160311-1742-B4952-installer-standalone.jar against a fresh workspace, then launching it thus: {code}./jbdevstudio -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://devstudio.jboss.com/10.0/aeri-discovery{code} Also tried adding the -D flag directly into the jbdevstudio.ini file. In both cases, I get this when I go to Window > Prefs > General > Error Reporting > Servers... !aeri-in-jbds10.png! But I can't get the AERI reporting to fire when I cause problem in p2, as suggested above. And, unlike in JBDS 9.1.0.CR1, there's not even a JBoss Tools aeri tracker (see https://issues.jboss.org/browse/JBDS-3566?focusedCommentId=13175673&p... ) was (Author: nickboldt): I can't make Aeri work in JBDS 10.0.0.Alpha1. I've created a dummy aeri-discovery site here: https://devstudio.jboss.com/10.0/aeri-discovery/ I've tried installation of jboss-devstudio-10.0.0.Alpha1-v20160311-1742-B4952-installer-standalone.jar against a fresh workspace, then launching it thus: {code}./jbdevstudio -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://devstudio.jboss.com/10.0/aeri-discovery{code} Also tried adding the -D flag directly into the jbdevstudio.ini file. In both cases, I get this when I go to Window > Prefs > General > Error Reporting > Servers... !aeri-in-jbds10.png! But I can't get the AERI reporting to fire when I cause problem in p2, as suggested above. -- This message was sent by Atlassian JIRA (v6.4.11#64026)