Hi Robert Another option might be to use "mongo" as an additional run mode. I.e. run mode "oak" would select the Oak repository implementation and run mode "mongo" would add some configuration in order to activate the mongo persistence.
I could imagine various pre-configured aspects for Oak, e.g. whether a file datastore should be used or not. So examples might be: oak: Oak repository on TarMK with blobs stored in segments oak,datastore: Oak repository on TarMK with blobs in datastore oak,mongo,datastore: Oak repository on Mongo with blobs in datastore WDYT, would that be a viable alternative? Regards Julian On Mon, Mar 23, 2015 at 2:21 PM, Robert Munteanu <[email protected]> wrote: > Hi, > > I'm going to take a quick look at SLING-4050 and will probably add a new > runmode for Mongo. > > I noticed that we currenty define two exclusive run modes for the > Launchpad: jackrabbit and oak. For SLING-4050 I would define the third > one: oak_mongo . I find that it would be better to rename the oak > runmode to oak_tar - as it uses the TarMK backend, but I'm not sure of > the implications. The 'oak' runmode has not been released with Launchpad > 7 so the only people affected would be the ones using -SNAPSHOT > releases. > > Does anyone see any issues with renaming the oak runmode to oak_tar ? I > will handle all the Maven/Jenkins stuff if we agree to do that. > > Cheers, > > Robert >
