JBoss Tools is made of a lot of plugins coming from different component, and that are aggregated for ease their installation. There are a lot of repositories. This page is intended to explain what are our repositories, what are they aimed to, and where they are coming from:

General process

Here is the general process of the lifecycle of sites in the build.

For each branch in progress, It consists in:

1. Build all common stuff (parent, target-platforms, requirement site)
2. Build each component independently
3. Each component repository is published to download.jboss.org
4. A development composite repository is used as a single entry point for all component repositories
5. Some JBoss Tools site (which is equivalent to the one to be released) are continuously created from the composite site. It contains a very recent version of each component, with right categories and so on. A test site is also created, containing only test-related stuff.
6. After a code-freeze, the result site is promoted as a dev milestone, it is then validated by QE
7. After several milestones and validation from QE, we get a release

The same applies to SOA components.

Some additional steps exist to also build JBDS site and products continuously, following the same lifecycle.

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/diagrams/JBDS_Aggregation.png Repositories / Update-Sites

Requirements / Target-platfoms sites / Mirrors

These site are mirrors of dependencies of JBoss Tools. They are here to provide more performance and to ensure we have a backup of everything we depend on.

JBT (non-SOA)

JBT SOA