Hi, On Tue, May 27, 2014 at 10:36 AM, Michael Dürig <mdue...@apache.org> wrote: > This is not about different jars but about setting it up as a OSGi container > into which the respective bundles could get deployed.
We can turn the jar in to an OSGi container, but why not ship everything everything we can by default? I definitely want to avoid the situation like in Sling where getting the software to work requires non-trivial compilation of multiple different components. I should be able to simply download the latest version of Oak and have it working right out of the box with no extra steps. BR, Jukka Zitting
