[jboss-dev-forums] [JBoss Tools Development] - JBoss Central - How Does It Work?

Nick Boldt do-not-reply at jboss.com
Tue Jan 29 18:01:26 EST 2013


Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document:

"JBoss Central - How Does It Work?"

To view the document, visit: https://community.jboss.org/docs/DOC-48297

--------------------------------------------------------------
JBoss Central, based on  http://wiki.eclipse.org/Mylyn/Discovery Mylyn Discovery, is in part a UI for installing new features into Eclipse or JBDS. It provider a richer, yet simpler UI than what Eclipse's p2 Install Manager provides out of the box. 


*The Software/Update tab in Central is backed by three levels of metadata:*

* directory.xml file listing 1 or more discovery plugins (eg., 1 for the Core features, 1 for the Integration Stack (formerly SOA Tooling) features)

* discovery plugin(s), which define groups of features ("Connectors") to be installed. This amounts to little more than a plugin.xml and some icons.

* update site(s) referenced by the discovery plugin(s), which host the features to be installed. Sites can be 3rd party vendors' sites, or can be mirrored on download.jboss.org / devstudio.jboss.com for better guarantee of performance / version. Each connector can only define a SINGLE URL for that group of features, however. But that single URL can be a composite site, which in turn points to more than 1 site.


*There are two simple rules to follow when writing your discovery plugin.xml:*
* connectorIDs must be stable - should not change between releases

* Where license terms permit, 3rd party content should be mirrored first onto download.jboss.org and/or devstudio.jboss.com, so that the site content can be more easily controlled / guaranteed


*How about some working examples?*

* *JBoss Tools 3.3**  http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-directory.xml http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-directory.xml (Source:  https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/updates/stable/indigo/jbosstools-directory.xml jbosstools-directory.xml)* Contains both Core and SOA - points at the following jars:* org.jboss.tools.central.discovery_.*.jar (Source:  https://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/central/plugins/org.jboss.tools.central.discovery/plugin.xml plugin.xml)
* org.jboss.tools.central.discovery.soa-tooling_*.jar (Source:  https://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/build/aggregate/soa-site/plugins/org.jboss.tools.central.discovery.soa-tooling/plugin.xml plugin.xml)

* Each jar's plugin.xml then lists a number of connectors, which are groups of features wrapped by a simpler UI than what Eclipse's p2 Install Manager provides out of the box.



* *JBoss Developer Studio 5.0**  https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml (Source:  http://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/5.0/devstudio-directory.xml devstudio-directory.xml)* Contains both Core and SOA - points at the following jars:* com.jboss.jbds.central.discovery_*.jar (Source:  https://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/plugins/com.jboss.jbds.central.discovery/plugin.xml plugin.xml)
* com.jboss.jbds.central.discovery.soa-tooling_*.jar (Source:  https://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product-soa/plugins/com.jboss.jbds.central.discovery.soa-tooling/plugin.xml plugin.xml)

* Each jar's plugin.xml then lists a number of connectors. 



* *JBoss Tools 4.0**  http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-directory.xml http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-directory.xml (Source:  https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/updates/stable/juno/jbosstools-directory.xml jbosstools-directory.xml)* Contains both Core and SOA - points at the following jars:* org.jboss.tools.central.discovery_.*.jar (Source:  https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.0.x/central/plugins/org.jboss.tools.central.discovery/plugin.xml plugin.xml)
* org.jboss.tools.central.discovery.soa-tooling_*.jar (Source:  https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.0.x/aggregate/soa-site/plugins/org.jboss.tools.central.discovery.soa-tooling/plugin.xml plugin.xml - +*SUBJECT TO CHANGE*+)

* Each jar's plugin.xml then lists a number of connectors.



* *JBoss Developer Studio 6.0**  https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml https://devstudio.jboss.com/updates/6.0/devstudio-directory.xml (Source:  http://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/6.0/devstudio-directory.xml devstudio-directory.xml)* Contains both Core and SOA - points at the following jars:* com.jboss.jbds.central.discovery_*.jar (Source:  https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/plugins/com.jboss.jbds.central.discovery/plugin.xml plugin.xml)
* com.jboss.jbds.central.discovery.soa-tooling_*.jar (Source:  https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product-soa/plugins/com.jboss.jbds.central.discovery.soa-tooling/plugin.xml plugin.xml - +*SUBJECT TO CHANGE*+)

* Each jar's plugin.xml then lists a number of connectors.
* In JBDS 6, these connectors (feature groups) are now labelled as "Tested" or "Supported".
--------------------------------------------------------------

Comment by going to Community
[https://community.jboss.org/docs/DOC-48297]

Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2129]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20130129/2402802c/attachment-0001.html 


More information about the jboss-dev-forums mailing list