Fork me on GitHub

Building from sources

Building OWNER from the sources has some advantages. For instance you can get the latest features still under development on GitHub master branch.

Building OWNER requires following software being installed and configured in your system:

  • JDK 7 or superior.
  • Maven 3.0.5 or superior (Maven 2 should also be ok).
  • GIT any recent version should be ok.

Java 5 and 6 are supported until OWNER 1.0.9. With OWNER 1.0.10 we introduced Java 9 support and we dropped Java 5 and 6 support, so if you use JDK prior to 7 you need to use OWNER 1.0.9.

Then follow these steps:

# Download the sources
$ git clone owner
$ cd owner
# Compile, execute test, and generate the artifacts
$ mvn install

This will build and install OWNER jars in your local maven repository. At the end of the process, you should find the generated artifacts in the target subdirectory.


The above examples uses the https url to clone the GIT repository, alternatively - if your firewall allows - you can use the GIT native URL that may be faster: git://

Building with support for Java 8 and superior

Since version 1.0.6 OWNER supports some language features introduced by Java 8 and superior, such as default methods in interfaces.

The support classes for these features are encapsulated in the maven module called owner-java8 that gets included into the build process only when maven is invoked from JDK 8.

Building a specific version

The git clone command downloads the full repository with the complete history on your local computer. That also contains tags for the released versions.

For instance, if I want to build the version 1.0.2

# as example, this time we use the git:// URL
$ git clone git:// owner
$ cd owner
# show all available tags
$ git tag -l
$ git checkout owner-1.0.2
HEAD is now at d2e4bbf... [maven-release-plugin] prepare release owner-1.0.2
$ mvn install

Please refer to GIT documentation to learn how to work with tags.

Running the tests

OWNER codebase is very compact and fully tested.

To execute the tests, you need maven properly installed and configured in your system, then run the following command from the project root:

$ mvn test

Continuous Integration

You can access latest builds from Jenkins and Travis websites.