On Sun, Feb 9, 2014 at 9:49 AM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > Hi, > > On Sun, Feb 9, 2014 at 4:05 AM, Davide Giannella > <giannella.dav...@gmail.com> wrote: >> It would make for example a lot easier to inject a CommitHook like a >> custom index. So far the only way to achieve so is to recompile the >> oak-run adding .with(new MyIndexProvider()) while I'd rather add a >> Service implementation the OSGi whiteboard. > > Some of us prefer to recompile the jar. :-) > > Of course that doesn't mean we couldn't do both. If someone's up to > it, an OSGi-based runnable Oak jar would be a nice contribution.
I played around with the felix runtime and gogo shell in [1] but didn't pursue this further. the problem is, that without a "launchpad" (eg [2]) the bootstrapping is tedious. regards, toby [1] https://github.com/tripodsan/jackrabbit-oak/tree/OAK-17/oak-felix [2] http://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html On Sun, Feb 9, 2014 at 9:49 AM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > Hi, > > On Sun, Feb 9, 2014 at 4:05 AM, Davide Giannella > <giannella.dav...@gmail.com> wrote: >> It would make for example a lot easier to inject a CommitHook like a >> custom index. So far the only way to achieve so is to recompile the >> oak-run adding .with(new MyIndexProvider()) while I'd rather add a >> Service implementation the OSGi whiteboard. > > Some of us prefer to recompile the jar. :-) > > Of course that doesn't mean we couldn't do both. If someone's up to > it, an OSGi-based runnable Oak jar would be a nice contribution. > > BR, > > Jukka Zitting
