Using Jena with Apache Maven

Apache Maven is a tool to help Java projects manage their dependencies on library code, such as Jena. By declaring a dependency on the core of Jena in your project's pom.xml file, you will get the consistent set of library files that Jena depends on automatically added too.

This page assumes you have Maven installed on your computer. If this is not the case, please read and follow these instructions.


Released maven artifacts are mirrored to the central maven repositories. This can take a few days.

The Jena repositories at Apache are:

Stable Jena releases are automatically mirrored by the central Maven repositories, so there will normally be no need to add any extra repositories to your pom.xml or settings.xml.

Specifying Jena as a dependency

This is how to specify in your pom.xml file the dependency on a version of Jena:


This will transitively resolve all the dependencies for you: jena-core, jena-arq, jena-tdb and jena-iri and their dependencies.

Note the use of <type>pom</type> above. This does not work in all tools. An alternative is to depend on jena-tdb, which will pull in the other artifacts.


The version number of TDB needs to be checked - it is not the same as apache-jena.

Other modules need to be added separately, for example:


Please check for the latest versions.

Major Artifacts

Jena provides a number of maven artifacts as delivery points.
There are also a number of maven artifacts used as part of structuring Jena development.

Artifact ID Packaging (<type>) Description
apache-jena-libs pom A POM artifact that may be referenced to pull in all the standard Jena Libraries (Core, ARQ, IRI, and TDB) with a single dependency.
apache-jena pom The binary distribution
apache-jena-fuseki pom Fuseki2 distribution
apache-jena-osgi pom Jena as an OSGi bundle
jena-sdb jar SDB (SQL based triple store). SDB should only be used when there is an absolute requirment on using SQL. TDB is to be preferred.
jena The formal released source-released for each Jena release. This is not a maven-runnable set of binary files
jena-spatial jar SPARQL Spatial Search. Included in Fuseki.
jena-text jar SPARQL Text Search. Included in Fuseki.
jena-csv jar A simple CSV mapping to RDF and amenable to SPARQL
jena-elephas pom A collection of tools for working with RDF on the Hadoop platform
jena-fuseki-war war WAR file for Fuseki
jena-security jar Security (Permissions) wrapper around Jena RDF implementation.
jena-maven-tools maven-plugin Maven Plugins, including schemagen
jena-jdbc-driver-bundle jar A collection of JDBC drivers
jena-querybuilder jar A utility package to simplify the building of ARQ queries in code.

There are also a number of artifacts used in development. The full list can be seen by browsing Maven

Released Jena artifacts

(This includes historic artifacts which are no longer active.)

You can run mvn dependency:tree to print the dependency tree.

Specifying dependencies on SNAPSHOTs

If you want to depend on Jena development snapshots, e.g. to get access to recent bug fixes, you should add the following to your pom.xml:


Build and install artifacts in your local Maven repository

If you want you can checkout the Jena sources, build the artifacts and install them in your local Maven repository, then you simply checkout the source tree and build with maven mvn install. This assumes you have Maven and Git installed:

cd jena
mvn clean install

Each of the modules can be built on it's own but they require the current snapshots and Jena parent POM to be installed.