shutdown orient database after bake has finished.

[ancho]

Using a local storage cache with db.store=local throws an exception
rerunning the bake task.

:bake FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':bake'.
> Cannot open local storage 'cache' with mode=rw

See stacktrace.

[coveralls]

Coverage decreased (-0.1%) to 67.377% when pulling 19c8e43 on ancho:feature/orientdb-shutdown into 2f6bd13 on jbake-org:master.

[jonbullock]

This was removed because it caused an issue while running in JBake's watch mode... but the cause of that may have been fixed since.... could you check if this still breaks watch mode?

[ancho]

Ah ok. Yes I can do that. I'm using jbake in combination with gradle and the continous task runner. Therefor I'm not aware of this breaking the watch mode for the cli.

[coveralls]

Coverage increased (+1.7%) to 69.231% when pulling b066a55 on ancho:feature/orientdb-shutdown into 2f6bd13 on jbake-org:master.

[ancho]

Hey Jon, yes it did break. When an instance of the Orient class gets created it calls startup() on the first instantiation. Calling shutdown() does a lot of stuff, like unregister engines.
The easiest solution is to check if count of engines is zero and call Orient.getInstance().startup() to reinitialize the orient database.
It works with watch mode for the cli and with a continuous gradle task.

On the long term it is better to decouple the startup and shutdown of the database from the bake method by passing the ContentStore to the Oven and handle it elsewhere I guess.

[jonbullock]

Thanks @ancho and I agree this needs to be looked at long term.