To add my bit to this idea. I am discovering that in order to develop
components, you end up with lots of dependencies back into the
ServiceMix project, most especially if you wish to be able to run unit
tests that instantiate a container in order to test components. This in
turn means that the
Yeah - actually we might want to do something like :
* container
* core tooling (just currently the jbi-maven-plugin)
* components
* archetypes
* other tooling like web applications, portal stuff, high end tools,
eclipse tooling etc
Since the archetypes are sort out outside of the tooling world
I agree with all of that; some refactoring of the build would be a
good thing. Using a common version number is a good thing too.
Just a thought; I wonder if we should split the tooling into 'maven
tooling' which will often be a core dependency on component's builds -
with other tooling (like ecl
I have been wondering about the possible restructuring of the ServiceMix
code tree and build to enable cleaner separation, smaller/quicker builds,
and the ability to separate out releases.
The idea has been bounced around a bit on IRC and I wanted to put it out
there for peoples thoughts.
The b
