merging caef3b67512a4ea2af2866da88b62d199e95177a
Merge pull request #796 from lassewesth/master

Using junit instead of ruby for acceptance tests
Increased guard timeout. This test should be waaay less flaky now on e.g. Windows
Guard timeout even more flexible on the upside
turning null parameter arguments into empty maps
Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph

o Changes priority of ORDER BY...LIMIT (PlanBuilder.TopX) so it is executed
  before updating the graph
o Changes so TopPipeBuilder waits for aggregation, but not for return
  expressions execution
o UpdateActionBuilder waits on slice to be done before accepting work
o SliceBuilder does not wait for updates to be done
Merge pull request #813 from systay/795

Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph
Revert "Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph"

This reverts commit b9814528621c95b2f4e8552f96ed3442fc18175a.
Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph

o SlicePipe will now empty the remainder if it is an updating query
Merge pull request #815 from systay/795

Fixes #795 - Inconsistent behaviour when using LIMIT and updates
Reintroduce 33725b268d8a7a024d55e2a65b3a338b488e6824
Update breaking test so that it passes with this change.
Random change of new URI() to URI.create()
Revert "Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph"

This reverts commit f299aa394be4563d3724573547b04f39ce6c4517.

Reverted because it is too close to GA and a workaround exists. Will be included again after the upcoming release.
Merge pull request #816 from digitalstain/server-log

Reintroduce 33725b268d8a7a024d55e2a65b3a338b488e6824
Remove potential race condition
Ensure that all config files have double newlines at the end
Tagging for version 1.9
Back to development version.
Puts up the access guard when handling a kernel panic to prevent users of
the database during the recovery to get random failures.

co-author: Lasse Westh-Nielsen
Changed the SecurityRules implementation so that all the rules are held within our code (rather than the underlying Web Server).

This has the most immediate benefit of fixing a bug whereby we seem to overwrite previously registered security rules with ones we register later. Dunno how that escaped us when we were building this first time around.

A second side effect is that we're a bit more portable.

Also my IDE formatted a bunch of code to the house style.
Changed POM back to 1.9-SNAPSHOT after inadvertently changing it to 2.0-SNAPSHOT somehow