On 06/10/2017 15:16, Robert Munteanu wrote: > Yeat another one can be embedding Oak in their project via > Maven/Gradle/etc dependencies . This is currently done in the oak- > examples module. Here we can consider defining an 'uber-pom' that is > used to pull in dependencies of a given Oak release.
This in my option is the only way we currently have Oak consumed by third parties. Even when we speak about the OSGi/Sling case, eventually it's a Maven dependency that gets either embedded (jackrabbit) in the bundle or referenced in an OSGi container. I don't really see the need of a quickstart. Probably one of the things we should start achieving from this discussion is: what do we want to have? I see independent module release with their own versioning. Do we, as community want to get there? Then, once we agree whether we want to get there or not, we can start looking at different projects that already do so, for instance Sling and see if such method would fit us. Eventually starting to highlight any problems we may have: backports and branching to mention a few. For all this last points I guess a wiki page would be a good place where to put all the ideas together. Davide
