There's no cleanly defined way to do that. I have in mind since several months to enhance the features maven plugin from Karaf to help doing that in a much easier way, i.e. have a simple way to create custom distributions on top of karaf by overlaying a set of karaf features + configuration files + branding (which could include renaming the main scripts to something different than karaf/karaf.bat) and let the plugin do all the work. There's a jira for that but nobody has had much time to work on that unfortunately. In the mean time, what ServiceMix does is using the maven assembly plugin to add all the required files on top of the unpacked karaf distribution and rebuild archives from that.
On Tue, Dec 28, 2010 at 20:41, Kit Plummer <kitplum...@gmail.com> wrote: > > Hey Karafers. > > I'm building a framework on top of Karaf, that is currently only adding the > "Branding" library and a few bundles. But, it is likely in the future I'll > need to remove some things, and more. Is there a "best way" strategy to > manage to relationship between my framework and Karaf? How does ServiceMix > do it? > > TIA, > Kit > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Branded-Karaf-tp2158363p2158363.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
