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 there are dependencies upon jars that are only in the
local maven repository if the current ServiceMix snapshot has been built
on the local machine. This obviously only occurs is you are developing
against a snapshot, but it is still an issue.
If the Servicemix build was refactored in such a way that the core jars
could be published independently, it would be easier to maintain a
development team working against a snapshot release without having to
run full builds everywhere, or try to keep a site proxy updated with all
the bits of ServiceMix.
Terry
