anchor.diff:  
   === Building and uploading Maven artifacts
   
  -We use the https://hudson.eclipse.org/rdf4j[Eclipse RDF4J Hudson CI instance] to build and deploy new releases to the Central Repository. To do this, simply log in to Hudson, and start the job named `rdf4j-deploy-release-ossrh-central`. The job will ask for the release tag as an input parameter, e.g. '2.2.1'. 
  +We use the https://hudson.eclipse.org/rdf4j[Eclipse RDF4J Hudson CI instance] to build and deploy new releases to the Central Repository.
  +To do this, simply log in to Hudson, and start the job named `rdf4j-deploy-release-ossrh-central`.
  +The job will ask for the github project and release tag as an input parameters, e.g. 'rdf4j' and '2.2.1'.
   
   This Hudson job will automatically check out the release tag, build the project, and upload all artifacts to https://oss.sonatype.org/[OSS Sonatype]. After successful upload, it will also automatically invoke synchronization with the Central Repository. Note that after successful completion, the artifacts may not be available on the Central Repository for several hours. 
   
  
positive.code: release while the _develop_ version uses the next expected major/minor
  release number, such as 2.1-SNAPSHOT and 2.2-SNAPSHOT respectively
  (after a 2.1.x release, but before any 2.2.x releases are made public).
  
  == Workflow
  
  
negative.code: 
  === Building the SDK and onejar
  
  1. Check out the release tag of https://github.com/eclipse/rdf4j[rdf4j]
  2. From the root directory, execute the following:
  
     mvn -Passembly clean install -DskipTests
  
  3. Repeat the above steps for https://github.com/eclipse/rdf4j-storage[rdf4j-storage] and https://github.com/eclipse/rdf4j-tools[rdf4j-tools].
  4. Once this completes, the SDK and onejar can be found in `assembly/target` of the rdf4j-tools subproject.
  5. Verify that the SDK is complete by inspecting its contents (in particular, check that javadoc is included).
  
  === Uploading the SDK and onejar
  
  