If you follow the download links from the download section at openRDF.org you'll find that there are a number of different files that you can download. Which one you need depends on what you want to do with it:
openrdf-sesame-(version)-sdk.tar.gz. This is a GNU-zipped tar archive of the complete binary version of the Sesame SDK. It includes all the Sesame libraries packaged as jar files and a set of Web Archive (.war) files for easy deployment of Sesame's web applications (see Chapter 5, Server software installation). It also includes documentation (such as this user manual, and the API documentation), as well as startup scripts for the Sesame command console (see Chapter 6, Sesame Console).
openrdf-sesame-(version)-sdk.zip. This is a zip archive that has the same contents as the tar.gz file mentioned before.
openrdf-sesame-(version)-onejar.jar. This is a Java Archive (.jar) file containing all the relevant Sesame libraries. The main purpose of this jar file is easy inclusion of all Sesame components when using it as an embedded component/library in your own application: you only need to add this one jar file to your classpath and you can start programming against it.
The Sesame libraries are also available as artifacts in a Maven repository. This Maven repository is located at http://repo.aduna-software.org/maven2/releases/. Developers using Maven can use this repository to automatically resolve library dependencies and to get the latest released versions of each library. See Chapter 4, Setting up to use the Sesame libraries for more information on how to set up your POM and which dependencies to include.
For instructions how to use the Maven build system, see http://maven.apache.org/.
Sesame's source code is available from our Subversion (SVN) repository:
There is an SVN Web Viewer available as well at http://repo.aduna-software.org/websvn/listing.php?repname=aduna&path=/org.openrdf/sesame/.
Source code for each release can be found in the
tags directory, the development version of the code
is in the
trunk directory. Branches exist for each
major release (2.4, 2.5, 2.6, etc.), with consecutive minor releases
(2.6.1, 2.6.2, etc.) being developed within that branch.