anchor.diff:  * OmniJ https://www.omnilayer.org/OmniJ/groovydoc/[GroovyDoc]
   * OmniJ https://ci.omni.foundation/job/OmniJ/[Unit Test Results] (currently unavailable)
   
  -=== OmniJ Maven Artifacts
  +=== Including the OmniJ Maven Artifacts (JARs) in your build
   
   WARNING: These binaries have not been audited. Use only on TestNet or RegTest.
   
  -Although the API is changing, binary packages are available on https://gitlab.com/OmniLayer/OmniJ/-/packages[Gitlab.com]. You can download JARs or use the provided Maven coordinates to link to them directly from your `pom.xml` or `build.gradle`.
  +Although the API is changing, binary releases are available on https://gitlab.com/OmniLayer/OmniJ/-/packages[Gitlab.com]. You can download JARs or use the provided Maven coordinates to link to them directly from your `pom.xml` or `build.gradle`.
   
   ==== Maven
   
  -Add the following to your `pom.xml`:
  -
  -[source]
  -----
  -<repositories>
  +Add the following to the `<repositories>` section of your `pom.xml`:
  +
  +[source, xml]
  +----
     <repository>
       <id>omnij-gitlab-maven</id>
       <url>https://gitlab.com/api/v4/projects/26583853/packages/maven</url>
     </repository>
  -</repositories>
  -----
  +----
  +
  +In the `<dependencies>` section of your `pom.xml` add a `<dependency>` element that references the OmniJ JAR that you need. For example if you are using classes from `omnij-core` add the following `<dependency>` configuration:
  +
  +[source, xml, subs="attributes+"]
  +----
  +    <dependency>
  +      <groupId>foundation.omni</groupId>
  +      <artifactId>omnij-core</artifactId>
  +      <version>{omnij-version}</version>
  +    </dependency>
  +----
  +
  +If you are using the `omnij-jsonrpc` JAR, add the following:
  +
  +[source, xml, subs="attributes+"]
  +----
  +    <dependency>
  +      <groupId>foundation.omni</groupId>
  +      <artifactId>omnij-jsonrpc</artifactId>
  +      <version>{omnij-version}</version>
  +    </dependency>
  +----
  +
   
   ==== Gradle
   
   Add the following to the `repositories` section of your `build.gradle`:
   
  -[source]
  +[source, groovy]
   ----
       maven { url 'https://gitlab.com/api/v4/projects/26583853/packages/maven' }
   ----
   
  +In the `dependencies` section of your `build.gradle` add an `implementation` configuration that references the OmniJ JAR that you need. For example if you are using classes from `omnij-core` add the following `implementation` configuration:
  +
  +[source, groovy, subs="attributes"]
  +----
  +    implementation "foundation.omni:omnij-core:{omnij-version}"
  +----
  +
  +If you are using the `omnij-jsonrpc` JAR, add the following:
  +
  +[source, groovy, subs="attributes"]
  +----
  +    implementation "foundation.omni:omnij-jsonrpc:{omnij-version}"
  +----
   
   === Building OmniJ
   
  -The only prerequisite for building OmniJ is having Java JDK 8 or later installed. All other prerequisites are downloaded automatically by the http://gradle.org/docs/current/userguide/gradle_wrapper.html[Gradle Wrapper] script.
  +The only prerequisite for building OmniJ is having Java JDK 11 or later installed. All other prerequisites are downloaded automatically by the http://gradle.org/docs/current/userguide/gradle_wrapper.html[Gradle Wrapper] script.
   
   . Check out this project using Git
   
  
positive.code: +
  The above examples are for the Consensus Test, to run the other test suites replace the `:omnij-rpc:consensusTest` Gradle target with `:omnij-rpc:regTest` for the Omni RegTests or with `:bitcoin-rpc:regTest` for the Bitcoin RegTests.
  
  == Running the tests from Jenkins
  
  To run the test from Jenkins we are using the following (UNIX) shell scripts:
  
  
negative.code: 
  . Build and test with the provided Gradle wrapper scripts. For Unix/Mac:
  
      ./gradlew build
  +
  or for Windows:
  
      ./gradlew.bat build
  
  After a successful build, each `omnij-_module_` JAR can be found in a standard location:
  
  