[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17964: ------------------------------------ We have two options: a) list feature(s) and a URL from which the feature(s) can be installed - this is how the JBDS and JBT entries work b) provide NO URL: just a description and link to the compatible JBDS marketplace entry - https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-ke... IMHO ( b ) is better because it will put eyeballs onto JBDSIS without splitting the install statistics across two solutions. We already split our user base between JBT and JBDS, resulting in a lower position in the standings of "top 10 solutions". If we further split that user base into 2 more buckets (JBT IS and JBDS IS) we'll lose our pole position in the top ten. ( b ) is also better because it doesn't provide yet another way to install JBDSIS which needs to have GSS support. All we're doing is driving traffic to JBDS and JBoss Central, which uses the existing supported install path. -- This message was sent by Atlassian JIRA (v6.2.6#6264)