On Mon, 2014-12-15 at 19:11 +0000, Bruce Edge wrote: > re-send in plain-text in attempt to fix indentation strip.
> >>If you are looking for a launchpad release, people typically > >>build their own launchpads, based on their needs. I personally would > >>start with the latest SNAPSHOT launchpad and customise it for my needs. > >> > >> > > > >Does this refer to modifying > >./launchpad/builder/src/main/bundles/list.xml to contain the desired > >services? Yes. Just to be clear, copy in a different project and adjust :-) > >Still reading up on run modes. > > > >Will this mechanism prevail long term or is the goal to move to something > >like the crankstart launcher, which, as I read, may eliminate the need > >for run modes. [3] I think run modes are here to stay. We use them at least to differentiate between jackrabbit and oak, and might refine the oak runmode depending on the choice of persistence with oak, e.g. oak_tarmk and oak_mongo [4]. As for the launcher, the latest incarnation is the Sling Provisioning Model + SlingStart, see [5]. > > > >So, this in the default sling.properties: > >sling.run.mode.install.options=jackrabbit,oak > >implies that both jackrabbit and oak run modes are to be installed such > >that either is selectable at runtime? IIRC these runmodes are install-only. Once you start with oak you can't switch to jackrabbit. You can of course use 'transient' run modes, for instance to separate instances by role 'dev', 'stage', 'prod' or any other classification that you see fit. > >What’s the status of the oak integration in this context? Is there a > >roadmap for this integration work? > >Is this tracked in the sling mailing list or elsewhere? > > > >The oak list is probably more relevant here but I feel like it’s a > >difficult time to start a new JCR project now as oak is purported to fix > >all of jackrabbit’s ills, yet is not ready for prime time use. The good part about using the JCR API is that you can start development on Jackrabbit 2.x and then migrate to Oak with no API changes. And it works better than switching relational databases :-) As for prime-time-readiness, Oak is ready for prime-time, but our integration still falls short. Although if you aim to deploy on Oak, I'd encourage you to start development against Jackrabbit and switch later to Oak . We'll have to tackle perfecting the Oak integration sooner rather than later. [4]: https://issues.apache.org/jira/browse/SLING-4050 [5]: http://sling.apache.org/documentation/development/slingstart.html
