I'd say keep the default assembly should be OK, only including bundles used by default boot features should be good. －－－－－－－－－－－－－ Freeman(Yue) Fang
Red Hat, Inc. FuseSource is now part of Red Hat On 2014-2-19, at 下午6:46, Gert Vanthienen wrote: > L.S., > > > Just noticed Krzysztof's comment about the how and why of the > apache-servicemix-full assembly in JIRA and think it's worth having a > quick discussion about which of these assemblies we want to keep > around going forward. > > Right now, we have 3 variations of our assembly in ServiceMix 5: > - The default assembly has a setup that includes the base CXF, Camel > and ActiveMQ bits and preinstalls those as boot features > - The minimal assembly actually has none of these things preinstalled, > it's just a plain Karaf with the feature URLs (among a few other > things) preconfigured - not sure how much this one is used though > - The full assembly is identical to default assembly, but the /system > folder contains all bundles for all optional features. This makes it > easy for people to use ServiceMix on servers that have no direct > connection to the internet. This one is probably used a bit more (I > usually install this one myself), but we are struggling to keep it > below the maximum 350000000 bytes distribution size (which is already > an exception to the rule at the ASF) and as issue > https://issues.apache.org/jira/browse/SM-2241 is showing, it is prone > to be impacted by any kind of error in any of our dependencies' > features files. > > For ServiceMix 5 and other upcoming versions, which of these > assemblies do we want to keep around? > > > Regards, > > Gert Vanthienen
