Hi, On Tue, May 27, 2014 at 10:53 AM, Michael Dürig <[email protected]> wrote: > Because > >>> increase flexibility, test and showcase OSGi readiness of Oak, >>> resolve version conflicts (e.g. Lucene), let others easily plug in >>> their own stuff (e.g scripting language through JSR-223).
Fair enough, but doing this does introduce a major entry barrier to just quickly trying things out, which IMHO is a big problem. I have no objections to shipping an OSGi container if people find that useful, but I do object to dropping functionality because of that. How about doing something like that in a separate component and leave oak-run as-is? BR, Jukka Zitting
