Page History

...

If you browse the URLs below, you will find a subdirectory for every component, neatly organized by component type. Every JBI component has its own trunk, branches and tags, so it 's really becomes a little project on it's its own in the SVN repo. This allows us to develop evolve and release all the components independently.

An example: http://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-bean^{Image Modified} contains a trunk, branches and tags for the servicemix-bean component.

However, in the same location, there is one special subdirectory called components-pom. It doesn't contain any components itself, but it uses only contains links to the trunk directory of every component, using an advanced SVN technique called svn:externals to make it easier to develop on different component. If you checkout this components-pom directory, you'll end up with . This allows a developer to easily checkout the latest development version of every components, organized by component type (subdirectory bindings contains the binding components, engines contains the service engines, ...)all components in a single operation.

Browsing the Source Tree

Web Browsing of SVN

...

To check out the source code for all components at once, you can use this SVN command to checkout the components-pom directory:

svn co http://svn.apache.org/repos/asf/servicemix/components/components-pom

...

ServiceMix committers will usually check out the entire component tree all components at once, using the command:

...