If you have added new features in your master branch, you need to let me
know what they are, so that:
a) they can be properly categorized and aggregated
b) they can be added to the Eclipse Marketplace entry (coming for Beta1)
c) they can be added to the install test job , which drives the
creation of the aggregate
PLEASE NOTE: if you have new features which are simply *children of
existing features*, like org.jboss.tools.archives.scanner.feature is
included in org.jboss.ide.eclipse.archives.feature, then just make sure
that the parent (containing) feature includes (not depends on, but
INCLUDES) the child  and you should be fine. Nothing more to do here.
THEREFORE, if you DO have *new features*, I need to know 4 things:
i) feature name, eg., org.jboss.tools.archives.scanner.feature
ii) category/ies in which should it be included, eg., CoreTools
("Abridged JBoss Tools") or AdditionalTools (everything else).
You can also put a feature into a secondary category to provide extra
"branding", eg., CloudTools, MavenTools, MobileTools. You can see them
here , , .
iii) Should it be included in the Hibernate Tools, Web Tools (JBoss AS
server adapter install site), or Core Tests (test features only) site
too? See , , .
If so, please specify the category/ies in which to include it. A PR
would be ideal, eg., against this file .
iv) Should it be included in the Eclipse Marketplace default install?
Normally this done simply by adding it to the CoreTools category.
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio