Like we have for JBT, we need that:

a) the update site for JBDS core contain a devstudio-directory.xml file: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.updatesite/product/devstudio-directory.xml
b) it be linked from the site's index.html page (to support mirrors)
c) the directory file link to a different discovery plugin, available only in JBDS: ~/trunk/product/plugins/com.jboss.jbds.central.discovery
d) this plugin must be wrapped w/ a feature and published onto the update site: ~/trunk/product/features/com.jboss.jbds.central.discovery.feature
e) readme files explaining how to access the different versions of the file for testing purposes: ~/trunk/product/README.Central.

.testing.txt

–

f) tweak jbdevstudio.ini to load the correct URL for the site:

... -vmargs -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml

g) update the releng guide publishing instructions / email template for this new tweak to record README/testing information for QE; also ensure that the discovery jar's plugin.xml points at the correct URL for downloading features, eg., http://devstudio.jboss.com/updates/5.0/soa-tooling/ vs. http://devstudio.jboss.com/updates/5.0/staging/soa-tooling/

h) tweak discovery plugin's plugin.xml to externalize the URL from which JBT/JBDS bits are installed

i) test running JBDS using new -Djbds.soa.site=http://some.staging.site/latest/ and document the QE process for running w/ these flags for testing Central