On Fri, Apr 25, 2008 at 6:22 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> I'd like to restart the discussion around this.  My opinion is that we
>  need to extract the components from the servicemix 3 build, so that
>  they can be shared more easily between servicemix 3 and servicemix 4.
>  I'm still not sure how to do that, because the distribution includes
>  the components and the examples and the examples need the components
>  to be compiled.  It's a bit of a chicken and egg problem, so any
>  suggestion is welcome.

Actually we need to break up the entire monolithic build in ServiceMix
3 and here is what I propose:

1) The tooling dir should be moved to servicemix/smx3/tooling
2) The deployables dir should be moved servicemix/smx-components
(though this needs more attention because each component should be a
separate subproject with it's own release cycle and versioning)
3) The samples dir should be moved to
servicemix/smx-components/examples (we should probably consider moving
distributions/apache-servicemix/src/main/release/examples as well)
4) The common dir should be moved to servicemix/smx-components/common

Upon splitting the components and the tooling out into their own
suprojects, they will have their own release cycle and versioning.
However, we will also have to still do monolithic releases of each SMX
3 and SMX 4 a few times each year so that the components and examples
are included with each monolithic release (e.g., maybe four times per
year).

But before we commence on any of this work, I really wanted to get the
website refactoring worked out. That's another topic that needs
another discussion. I'll reply with my thoughts on this to the
discussion I started some weeks ago on the dev list.

Bruce
-- 
perl -e 'print unpack("u30","D0G)[EMAIL 
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/

Blog: http://bruceblog.org/

Reply via email to