[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18239: --------------------------------------------- It is clearly neither i'm suggesting. See my first comment: "The idea was that we don't need the entries for jboss tools based plugins in the actual central TP." That means that the content coming from JBT is *NOT* to be in central TP but into the main JBDS TP (the one used for creating the main updatesite). A talks about *all* JBT and putting in central - so that is not it. B talks about an additional updatesite - that is not what i'm suggesting either. And no, early access and central updatesites CANNOT be in the same updatesite - that have been discussed ad libitum before how that is not okey since: A) Earlyaccess IS NOT central B) if you add earlyaccess into central then users running Help > Check for updates (or install) will get earlyaccess content even though they have not enabled it. I would really appreciate if we stop having to return to that item again - central IS NOT earlyaccess and vice versa thus they cannot be intermingled. i suggest we park this and go through this during f2f or at least after CR2 since now is really not the time to such revamps that needs testing. -- This message was sent by Atlassian JIRA (v6.3.1#6329)