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:
$ java -jar oak-run.jar backup ...
and
$ java -jar oak-backup.jar ...
I rather prefer the former as it gives me everything in one package
and reduces maintenance overhead.
BR,
Jukka Zitting
