[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18239: ------------------------------------ [~maxandersen] you're right, Central is already a composite. I keep saying Central will composite this content because Central already composites it. [~mickael_istria] removing o.j.t.* isn't enough because these pieces don't exist in JBDS, only in JBT. Thus to provide them as part of the JBDS Central or EA experience, they have to exist somewhere (else). Choices include: a) leave them in the Central and EA target platform update sites (current state) b) move them to a new update site (proposed via this JIRA and the above PRs) which can be composited into the JBDS Central site* c) include the entire JBT update site in the JBDS Central site* (bad idea IMHO because we'll expose JBDS users to installing JBT content w/o it coming through the Central or EA UI; however this is simpler in that it doesn't require a new category.xml, but also eats more disk space and duplicates content in the Central composite) * - The JBDS Central site is a composite containing JBDS TP, JBDS update site, and JBoss Central. If we remove the o.j.t.* content from the JBoss Central target platform & update site, it will no longer be in the composite. Therefore it needs to come from somewhere else. -- This message was sent by Atlassian JIRA (v6.3.1#6329)