Sorry for the delayed reply, I had to simmer on this for a couple of days
before responding.
I am absolutely +1 on separating the components from the main distribution.
To solve the chicken and egg problem with the examples, perhaps the examples
could be part of the components subproject and available separately? This
idea just makes perfect sense to me, as does Bruce's idea to release the
components with their own lifecycle and versions.
More comments on Bruce's ideas inline below...
On Fri, Apr 25, 2008 at 8:40 AM, Bruce Snyder <[EMAIL PROTECTED]>
wrote:
> 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
+1 In particular the jbi-maven-plugin would be very nice to have as a
separate release lifecycle so that we can have the main build depend only on
a released version of this plugin. Then we are back to single phase builds
that will just work.
> 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)
+1 This makes perfect sense to me. There will certainly be additional
overhead of releasing each of the components separately and more often, but
I am hoping that by splitting the project up a bit with separate lifecycles,
we may also be able to leverage things like the maven release plugin to ease
some of the burden of doing these releases. I also think we would be doing
ourselves a favor on suport and mailing list issues because we can fix
specific issues on a specific component and do the release promptly without
worrying about where the main distribution is in its release cycle. I think
we could also possibly split the release duties amongst some of active
committers (since everyone has specific components that they take more
interest in) and get slightly more community involvement.
>
> 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)
+1 This might require more discussion of the actual details, but as I said
above I think this is the way to go.
> 4) The common dir should be moved to servicemix/smx-components/common
I haven't had time to ponder the technical implication so of this move, but
it sounds like a good given the other similar moves suggested.
>
>
> 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).
My initial thought on this is to make the server available standalone, and
then have a component distribution that has all components. In addition, I
think interim releases of individual components makes sense so that users
can get fixes for specific issues that get fixed. This one will require
some discussion and community input.
>
>
> 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.
Indeed, the web site and docs need some care and attention. I think it will
help to know the direction we are going to take with the above ideas, so
that we can keep them in mind while restructuring the web site.
>
>
> 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/
>
Chris
--
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Directory Server :: http://directory.apache.org
