Gert Vanthienen wrote: > > L.S., > > If you need a really trimmed down assembly, it's probably easier to > start with a plain Karaf and adding bundles for features using the > plugin as we do in ServiceMix itself - this will get you an assembly > with only the bundles for your features in there, which is what you > want, right? There's no tooling/commands/... for adding/removing > bundles from the /system folder in an existing assembly at the moment. > However... >
I think this is the crux of the issue -- when I examine what's along for the ride in our current, development ServiceMix footprint there are at least a few bundles which have snuck in over time that don't appear to be used by anyone (nice-to-haves) and, even though I can establish this by trial and error, I'd like to be able to systematically purge any that are unnecessary for our intentional capabilities. Gert Vanthienen wrote: > > We regularly get questions like 'my server is not connected to the > internet, could you add bundle x to the system folder', how about we > provide a means for people to start an assembly, tweak it by > adding/removing bundles and then export the result so it can be moved > into a constrained environment afterwards? We already have the > features-maven-plugin and an archetype for creating your own assembly, > but perhaps we should provide an easier way for people that are only > interested in preparing an assembly for a production deployment. > > Wdyt? > I think this is a fine idea, actually, and would help our cause at least a little. ----- "Professional coder on closed source. Do not attempt." -- View this message in context: http://servicemix.396122.n5.nabble.com/Stripping-down-a-ServiceMix-installation-for-compact-redeployment-tp4471273p4488613.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
