If you do some minor customization of Karaf config files and maybe packaging an extra jar for the lib directory such as bouncy castle, would that be fine with a kar? My thought is if I could prevent needing to redeploy a distribution when I need to make a Karaf system config change and instead just re-apply a new version of a KAR file to update the deployments..... Not sure if that will work how I'm hoping....
Ryan On Apr 14, 2015 2:17 PM, "Jamie G." <[email protected]> wrote: > Kars when you want a the full application deployed as one - custom > distribution when you have a full complex setup you need to deliver. > > Ex: An application composed of a bunch of routes -- a Kar would suffice. > Ex: A full SDN controller - build a distribution such as OpenDaylight or > NSOS. > > On Tue, Apr 14, 2015 at 3:37 PM, Ryan Moquin <[email protected]> > wrote: > > I was wondering if anyone could explain the situations when you would > use a > > custom distribution for Karaf vs a kar with the Karaf configurations > > customized? Is it preference? Or is there an advantage of one over the > > other? > > > > Ryan >
