On 27.5.14 4:26 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 9:47 AM, Michael Dürig <[email protected]> wrote:
On 27.5.14 3:33 , Jukka Zitting wrote:
Too heavy in which way?
Functionality wise. It is growing into a "chief cook and bottle washer". It
already does backup, benchmarking, simple console, debugging, server,
upgrade, and scalability testing.
How would splitting those responsibilities to different jars make any
difference? I.e. what's the essential difference between:
This is not about different jars but about setting it up as a OSGi
container into which the respective bundles could get deployed. This
would certainly increase complexity but also 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).
Michael
