anchor.diff:  * JDK 8
   * Apache Maven version 3.3.6 or higher
   
  -To build the project, run in the parent directory (i.e. `$KUDU_HOME/java`)
  -[listing]
  -----
  -$ mvn clean compile test-compile -Pjepsen
  +To build the project and install necessary Java packages into the local mvn
  +repository, run in the parent directory (i.e. `$KUDU_HOME/java`)
  +[listing]
  +----
  +$ mvn -Pjepsen -DskipTests clean install
   ----
   
   === Running
  
positive.code: *Jepsen DB node* roles. The machine where the above mentioned maven command
  is run plays *Jepsen control node* role.
  
  === Troubleshooting
  When Jepsen's analysis doesn't find inconsistencies in the history of operations
  it outputs the following in the end of a test:
  
negative.code: 21:41:42 0 failures, 10 errors.
  ----
  To get more details, take a closer look at the output of `mvn clojure:run`
  or at particular `jepsen.log` files in
  `$KUDU_HOME/java/kudu-jepsen/store/rw-register/<test_timestamp>` directory. A
  quick way to locate the corresponding section in the error log is to search for
  `^ERROR in \(` regex pattern. An example of error message from Jepsen's output:
  [listing]
  ----
  ERROR in (register-test-tserver-random-halves) (KuduException.java:110)
  expected: (:valid? (:results (jepsen/run! (tcasefun opts))))
    actual: org.apache.kudu.client.NonRecoverableException: can not complete before timeout: KuduRpc(method=IsCreateTableDone, tablet=null, attempt=28, DeadlineTracker(timeout=30000, elapsed=28571), ...
  ----
  
  The latter class represents more serious issue: a manifestation of
  non-linearizable history of operations. This is reported as _failure_ in the
  