On 27.5.14 5:13 , Jukka Zitting wrote:
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?
Users needn't be aware of the OSGi container inside if they just want to
quickly try something out. Running with e.g. the benchmark option would
still run the benchmark suite. The difference would be that in the
background we would start an OSGi container, deploy the relevant bundles
and off we go. We could even add all of the bundles all the time for
simplicity. This still serves all the purposes I outlined above. I.e.
easy to add own stuff and so on...
Michael
