I had a question yesterday about the makeup of the tuscany-base jar and the answer is so far its mainly been put together with just things i happened to find useful or look reasonable so i wonder if we should be a bit more consistent with it if users are going to be depending on it.
You can see all the dependencies it has by looking in the pom.xml but the main things included right now are: all tuscany core and base sca assembly interface.java implementation.java interface.wsdl binding.ws using jaxws-ri impl binding.rmi distributed domain and binding.sca using hazelcast implementation-web implementation-web jax-rs support with wink dependencies excluded implementation-web stripes support with stripes dependencies excluded host-jetty with dependencies excluded contribution-osgi/implementation-osgi/node-impl-osgi/extensibility-equinox/node-launcher-equinox with all dependencies excluded It has all the JDK6 included dependencies as provided scope so all the gives dependencies jars of: asm, cglib, and XmlSchema, wsdl4j, and hazelcast. The logic for what is there went something like this:- include minimum base to to get simplest implementation.jar component running in jdk6 and then anything that had no dependencies or only dependencies that are already required, or anything where the dependencies could reasonably be assumed to be already in the environment so they can be excluded (eg jetty, osgi, stripes). Following that logic the distributed domain support with hazelcast shouldn't really be there but it is so i guess i just decided distributed domain support was essential. So any comments on how better we could split things up? ...ant
