We welcome your contribution towards making Jena a better platform for semantic web and linked data applications. We appreciate feature suggestions, bug reports and patches for code or documentation.
If you need help using Jena, please see our getting help page.
You can help us sending your suggestions, feature requests and bug reports (as well as patches) using the Jena issue tracker.
You can discuss your contribution, before or after adding it to Jira, on the
email@example.com mailing list.
You can also help other users by answering their questions on the
firstname.lastname@example.org mailing list.
See the subscription instructions for details.
Please see the Reviewing Contributions page for details of what committers will be looking for when reviewing contributions.
You can also help us improve the documentation on this website by making use of the Apache CMS which drives the website.
Please see I’m not a committer on $project, which uses the CMS. Can I still use the CMS? for guidance on how to do this. This process allows you to suggest improvements to the project website as patches (because everything at Apache lives in SVN) and helps the wider community. Contributions to documentation are always welcome and considered just as valuable as code contributions.
You can click the Improve this Page button (top-right) on any page to instantly open the web based CMS editor. If prompted you
will need to use the username
anonymous and a blank password to log in. Use the [Diff] and [Mail Email] links to submit your proposed changes to the Apache Jena committers.
If you use Apache Maven and you are not afraid of being on the bleeding-edge, you can help us by testing our SNAPSHOTs which you can find in the Apache Maven repository.
Here is, for example, how you can add TDB version X.Y.Z-SNAPSHOT to your project (please ask if you are unsure what the latest snapshot version number currently is):
<dependency> <groupId>org.apache.jena</groupId> <artifactId>jena-tdb</artifactId> <version>X.Y.Z-SNAPSHOT</version> </dependency>
See also how to use Jena with Maven.
If you have problems with any of our SNAPSHOTs, let us know.
You can check the state of each Jena development builds on the Apache Jenkins continuous integration server.
You can find the Jena source code in the Apache git repository: https://git-wip-us.apache.org/repos/asf/jena.git
There is also a read-only mirror of Jena on GitHub:
git clone https://github.com/apache/jena.git cd jena mvn clean install
You can develop new contributions and work on patches using either the Apache-hosted git repository or the mirror on GitHub.
Alternatively, patches can be attached directly to issues in Jira
More Actions > Attach Files).
Please, inspect your contribution/patch and make sure it includes all (and only) the relevant changes for a single issue. Don’t forget tests!
If you want to test if a patch applies cleanly you can use:
patch -p0 < JENA-XYZ.patch
If you use Eclipse: right click on the project name in
Team > Create Patch or
Team > Apply Patch.
You can also use git:
git format-patch origin/trunk
Some Jena developers hang out on #jena on irc.freenode.net.
To better understand how to get involved and how the Apache Software Foundation works we recommend you read: