Our SCA binary distribution is over 100Meg now and there's still extensions and dependencies I've not added yet. This seems a little big considering we're trying to sell Tuscany as all svelte and light weight.
So what to do? The reason its so big is that every webapp sample and demo we have ends up including a copy of most of the runtime and dependencies. One solution could be to just ship fewer prebuilt webapp samples and demos. Another could be to change the way we do those samples so that each sample/demo is just a simple SCA contribution jar and you have to deploy that to some Tuscany runtime. We've already the webapp runtime that would work for that, and the Geronimo Tuscany support, and we could create another standalone runtime if you don't want to use Tomcat or Geronimo. What do people think, does the size matter, are there some other things we could do? ...ant
