Java Other
Permalink
Failed to load latest commit information.
bom [Jenkins release job] Preparing next development iteration Feb 15, 2017
cassandra [Jenkins release job] Preparing next development iteration Feb 15, 2017
core [Jenkins release job] Preparing next development iteration Feb 15, 2017
couchdb [Jenkins release job] Preparing next development iteration Feb 15, 2017
distribution [Jenkins release job] Preparing next development iteration Feb 15, 2017
documentation [Jenkins release job] Preparing next development iteration Feb 15, 2017
ehcache [Jenkins release job] Preparing next development iteration Feb 15, 2017
infinispan-remote [Jenkins release job] Preparing next development iteration Feb 15, 2017
infinispan [Jenkins release job] Preparing next development iteration Feb 15, 2017
integrationtest [Jenkins release job] Preparing next development iteration Feb 15, 2017
jipijapa [Jenkins release job] Preparing next development iteration Feb 15, 2017
modules [Jenkins release job] Preparing next development iteration Feb 15, 2017
mongodb [Jenkins release job] Preparing next development iteration Feb 15, 2017
neo4j [Jenkins release job] Preparing next development iteration Feb 15, 2017
performance [Jenkins release job] Preparing next development iteration Feb 15, 2017
redis [Jenkins release job] Preparing next development iteration Feb 15, 2017
src OGM-1195 Add RESOURCE_SPECIFICATION to ParentPad checkstyle rule Jan 3, 2017
travis OGM-1048 Travis - Stable URL for Cassandra download May 11, 2016
.gitattributes OGM-220 Fix remaining wrong line endings Jul 25, 2012
.gitignore OGM-1146 Properly ignore hibernate-noorm-release-scripts directory Aug 12, 2016
.travis.yml OGM-1234 Travis - Get the Neo4j version from the pom file Jan 11, 2017
README.md [Jenkins release job] README.md updated by release build 5.1.0.CR1 Feb 15, 2017
changelog.txt [Jenkins release job] changelog.txt updated by release build 5.1.0.CR1 Feb 15, 2017
how-to-release.md OGM-1144 Update the release process Sep 6, 2016
license.txt OGM-57 rename licence.txt to license.txt Apr 29, 2011
pom.xml [Jenkins release job] Preparing next development iteration Feb 15, 2017
settings-example.xml OGM-1090 Use Central first to get the artifacts Jun 17, 2016

README.md

Hibernate OGM

Version: 5.1.0.CR1 - 15-02-2017

Description

Hibernate OGM stores data in a NoSQL data grid using the Hibernate ORM engine.

The benefits are fairly obvious:

  • write your model once using well known JPA annotations and select the right NoSQL data grid for your project
  • Hibernate is familiar to many people
  • you end up being able to use all the tools of the Hibernate ecosystem such as Hibernate Search or Hibernate Validator

Checkout http://hibernate.org/ogm/ for more information.

Useful pointers

Latest Documentation:

Bug Reports:

Support:

Build instructions

The code is available on GitHub at https://github.com/hibernate/hibernate-ogm.

To run the full project build including tests for all backends, documentation etc. execute:

mvn clean install -s settings-example.xml

Note that for running the test suite against separately installed MongoDB and CouchDB servers their host name must be specified via an environment variable. See the sections below for the details.

To speed things up, there are several options for skipping parts of the build. To run the minimum project build without integration tests, documentation and distribution execute:

mvn clean install -DskipITs -DskipDocs -DskipDistro -s settings-example.xml

The following sections describe these options in more detail.

Importing sources in Eclipse

Import the project as any standard Maven project. This might trigger a dialog to automatically find and install additional m2e plugins: allow that.

Make sure that annotation processing is enabled in your project settings (see "Properties" - "Maven" - "Annotation Processing", the setting should be "Automatically configure JDT APT").

Integration tests

You can skip integration tests by specifying the skipITs property:

mvn clean install -DskipITs -s settings-example.xml

Documentation

The documentation is built by default as part of the project build. You can skip it by specifying the skipDocs property:

mvn clean install -DskipDocs -s settings-example.xml

If you just want to build the documentation, run it from the documentation/manual subdirectory.

By default, the following command only builds the HTML version of the documentation:

mvn clean install -f documentation/manual/pom.xml -s settings-example.xml

If you also wish to generate the PDF version of the documentation, you need to use the documentation-pdf profile:

mvn clean install -f documentation/manual/pom.xml -s settings-example.xml -Pdocumentation-pdf

Distribution

The distribution bundle is built by default as part of the project build. You can skip it by specifying the skipDistro property:

mvn clean install -DskipDistro -s settings-example.xml

Integration tests

Integration tests can be run from the integrationtest module and the default behaviour is to download the WildFly application server, unpack the modules in it and run the tests using Arquillian.

WARNING

Be careful when using on existing installation since the modules used by the build are going to be extracted into the server you want to run the test, changing the original setup.

MongoDB

For executing the tests in the mongodb and integrationtest/mongodb modules, by default the embedmongo-maven-plugin is used which downloads the MongoDB distribution, extracts it, starts a mongod process and shuts it down after test execution.

If required, you can configure the port to which the MongoDB instance binds to (by default 27018) and the target directory for the extracted binary (defaults to ${project.build.directory}/embeddedMongoDb/extracted) like this:

mvn clean install -s settings-example.xml -DembeddedMongoDbTempDir=<my-temp-dir> -DembeddedMongoDbPort=<my-port>

To work with a separately installed MongoDB instance instead, specify the property -DmongodbProvider=external:

mvn clean install -s settings-example.xml -DmongodbProvider=external

This assumes MongoDB to be installed on localhost, using the default port and no authentication. If you work with different settings, configure the required properties in hibernate.properties (for the tests in mongodb) and/or the environment variables MONGODB_HOSTNAME MONGODB_PORT MONGODB_USERNAME MONGODB_PASSWORD (for the tests in integrationtest/mongodb) prior to running the tests:

export MONGODB_HOSTNAME=mongodb-machine
export MONGODB_PORT=1234
export MONGODB_USERNAME=someUsername
export MONGODB_PASSWORD=someP@ssw0rd
mvn clean install -s settings-example.xml -DmongodbProvider=external

Finally, you also can run the test suite against the in-memory "fake implementation" Fongo:

mvn clean install -s settings-example.xml -DmongodbProvider=fongo

CouchDB

For running the tests in the couchdb module an installed CouchDB server is required. Specify its host name by setting the environment variable COUCHDB_HOSTNAME prior to running the test suite:

export COUCHDB_HOSTNAME=couchdb-machine

If this variable is not set, the couchdb module still will be compiled and packaged but the tests will be skipped. If needed, the port to connect to can be configured through the environment variable COUCHDB_PORT.

Cassandra

For running the tests in the cassandra module an installed Cassandra server is required. Specify its host name by setting the environment variable CASSANDRA_HOSTNAME prior to running the test suite:

export CASSANDRA_HOSTNAME=cassandra-machine

If this variable is not set, the cassandra module still will be compiled and packaged but the tests will be skipped. If needed, the port to connect to can be configured through the environment variable CASSANDRA_PORT.

Redis

For running the tests in the redis module an installed Redis server is required. Specify its host name by setting the environment variable REDIS_HOSTNAME prior to running the test suite:

export REDIS_HOSTNAME=redis-machine

If this variable is not set, the redis module still will be compiled and packaged but the tests will be skipped. If needed, the port to connect to can be configured through the environment variable REDIS_PORT.

Tests with the redis module can be started using a Makefile. The Makefile takes care of downloading and compiling a recent Redis version, starts a single Redis Standalone and four Redis Cluster nodes and can start the tests.

 make test # Make me happy and run tests against Redis Standalone and Redis Cluster
 make test-standalone
 make test-cluster

Commands to spin up/shut down the Redis instances:

make start
make stop

Neo4j

For running the tests in the neo4j and integrationtest/neo4j modules, by default the embedded Neo4j configuration is used.

If you want to run the tests on a remote server, you need to specify the profile neo4j-remote

mvn clean install -s settings-example.xml -Pneo4j-remote

This assumes Neo4j to be installed on localhost, using the default port and no authentication. If you work with different settings, configure the required properties in hibernate.properties and/or the environment variables NEO4J_HOSTNAME, NEO4J_PORT, NEO4J_USERNAME and NEO4J_PASSWORD prior to running the tests:

export NEO4J_HOSTNAME=neo4j-machine
export NEO4J_PORT=1234
export NEO4J_USERNAME=someUsername
export NEO4J_PASSWORD=someP@ssw0rd

Notes

If you want to contribute, come to the hibernate-dev@lists.jboss.org mailing list or join us on #hibernate-dev on freenode (login required)

This software and its documentation are distributed under the terms of the FSF Lesser Gnu Public License (see license.txt).