SVN repo layout
Move the ServiceMix 3 related tree under a single subtree
Here is the proposed SVN layout to accomodate the needs for SMX 4.
http://svn.apache.org/repos/asf/servicemix /m2-repo /sandbox /scripts /site /smx3 /tags /branches /trunk /smx4 /trunk
From the current layout, is would only involve the following commands:
svn mkdir https://svn.apache.org/repos/asf/servicemix/smx3 svn mv https://svn.apache.org/repos/asf/servicemix/tags https://svn.apache.org/repos/asf/servicemix/smx3/ svn mv https://svn.apache.org/repos/asf/servicemix/branches https://svn.apache.org/repos/asf/servicemix/smx3/ svn mv https://svn.apache.org/repos/asf/servicemix/trunk https://svn.apache.org/repos/asf/servicemix/smx3/ svn mkdir https://svn.apache.org/repos/asf/servicemix/smx4 svn mv https://svn.apache.org/repos/asf/servicemix/branches/servicemix-4.0 https://svn.apache.org/repos/asf/servicemix/smx4/trunk
Reorganize the Smx4 subtree
Inside the smx4 subtree, the layout would be as following:
http://svn.apache.org/repos/asf/servicemix/smx4 /parent /tags /branches /trunk /bundles /tags /branches /trunk /runtime /tags /branches /trunk /nmr /tags /branches /trunk /jbi /tags /branches /trunk ...
parent
would contain the root pom that all other poms must directly or indirectly inherit. This pom would contain informations related to ServiceMix in general and would inherit from the Apache one.
bundles
is a subtree containing all OSGified bundles. The content should not change much, but new additions may come from time to time, or bundles could be deprecated if their owning project provides direct support for OSGi.
runtime
contains the OSGi server described at Runtime
nmr
contains the NMR apis and implementation for ServiceMix
jbi
contains the JBI compatibility layer based on nmr
...