On Mon, Sep 13, 2010 at 10:48 AM, Simon Laws <simonsl...@googlemail.com> wrote: >> >> Simon and i chatted about this a bit, i'm still not really convinced >> about what the features give us and would still be interested in >> answers to the questions in the previous email about the ws and ejava >> features. I have made a new "base" feature from the shaded base jar >> and changed the shaded base to use that feature, is anyone more happy >> with it like that? >> >> ...ant >> > > Personally I like "base" rather "core" as we already have modules/core > so found the core feature a little confusing. Having said this I'd > like to understand a bit more about what the make up of base is or > should be. Looking at core vs base features I see... > > Core > ==== > tuscany-assembly > tuscany-assembly-xml > tuscany-assembly-xsd > tuscany-contribution > tuscany-core > tuscany-core-databinding > tuscany-core-spi > tuscany-databinding > tuscany-databinding-jaxb > tuscany-domain-node > tuscany-extensibility > tuscany-extensibility-equinox > tuscany-feature-api > tuscany-host-corba-jse > tuscany-host-http > tuscany-implementation-java-runtime > tuscany-interface-java > tuscany-interface-java-jaxws > tuscany-interface-wsdl > tuscany-monitor > tuscany-node-impl > tuscany-node-launcher > tuscany-node-launcher-equinox > tuscany-policy-security > tuscany-sca-client-impl > tuscany-shell > tuscany-xsd > > Base > ==== > tuscany-binding-hazelcast-runtime > tuscany-binding-rmi-runtime > tuscany-binding-ws-runtime-jaxws-ri > tuscany-contribution-osgi > tuscany-data-api > tuscany-domain-node > tuscany-endpoint-hazelcast > tuscany-endpoint-hazelcast-client > tuscany-extensibility-equinox > tuscany-host-jetty > tuscany-host-rmi > tuscany-implementation-osgi-runtime > tuscany-implementation-web-runtime > tuscany-launcher > tuscany-node-impl-osgi > tuscany-node-launcher-equinox > tuscany-sca-client-impl > tuscany-sca-client-javascript > tuscany-shell > tuscany-stripes > tuscany-wink > > So "core" references the basic modules required to get the runtime up. > Base does as well but it's not as clear cut. There are a few extra > things in there, stripes, wink etc. Also I assume it relies on > transitive dependencies for things like assembly etc. >
The shaded base includes more than the feature core mainly because it works and is used differently. When a uses uses the base jar they get that one jar and nothing else so it doesn't really matter if extra things are included in base as long as they don't drag in extra transitive dependencies, the only difference is the jar gets a little bigger but in most situations that doesn't matter. The core feature on the other hand brings in all the module jars it uses individually so the artifacts appear to users and if it did bring in extra stuff like tuscany-stripes then that would look odd to a user who was not using stripes. The base jar does include the hazelcast domain support, i guess really that should be separated out so its not dragged in when you're not using the distributed domain. ...ant
