If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories:
services/jbpm -> jbpm.esb
services/smooks -> smooks.esb
services/cbr/jbr -> cbr-jbr.esb
each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.