Hibernate ORM is a component/library providing Object/Relational Mapping (ORM) support to applications and other components/libraries. It is also provides an implementation of the JPA specification, which is the standardized Java specification for ORM. See Hibernate.org for additional information.
git clone git://github.com/hibernate/hibernate-orm.git
cd hibernate-orm
./gradlew clean build
The build requires a Java 8 JDK as JAVA_HOME.
Hibernate uses Gradle as its build tool. See the Gradle Primer section below if you are new to Gradle.
Contributors should read the Contributing Guide
See the guides for setting up IntelliJ or Eclipse as your development environment. Building Hibernate ORM is somewhat outdated, but still has
Hibernate makes use of Jenkins for its CI needs. The project is built continuous on each push to the upstream repository. Overall there are a few different jobs, all of which can be seen at http://ci.hibernate.org/view/ORM/
This section describes some of the basics developers and contributors new to Gradle might need to know to get productive quickly. The Gradle documentation is very well done; 2 in particular that are indispensable:
- Gradle User Guide is a typical user guide in that it follows a topical approach to describing all of the capabilities of Gradle.
- Gradle DSL Guide is quite unique and excellent in quickly getting up to speed on certain aspects of Gradle.
For contributors who do not otherwise use Gradle and do not want to install it, Gradle offers a very cool
features called the wrapper. It lets you run Gradle builds without a previously installed Gradle distro in
a zero-conf manner. Hibernate configures the Gradle wrapper for you. If you would rather use the wrapper and
not install Gradle (or to make sure you use the version of Gradle intended for older builds) you would just use
the command gradlew (or gradlew.bat) rather than gradle (or gradle.bat) in the following discussions.
Note that gradlew is only available in the project's root dir, so depending on your pwd you may need to adjust
the path to gradlew as well.
Gradle uses the concept of build tasks (equivalent to Ant targets or Maven phases/goals). You can get a list of available tasks via
gradle tasks
To execute a task across all modules, simply perform that task from the root directory. Gradle will visit each sub-project and execute that task if the sub-project defines it. To execute a task in a specific module you can either:
cdinto that module directory and execute the task- name the "task path". For example, in order to run the tests for the hibernate-core module from the root directory you could say
gradle hibernate-core:test
- build - Assembles (jars) and tests this project
- buildDependents - Assembles and tests this project and all projects that depend on it. So think of running this in hibernate-core, Gradle would assemble and test hibernate-core as well as hibernate-envers (because envers depends on core)
- classes - Compiles the main classes
- testClasses - Compiles the test classes
- compile (Hibernate addition) - Performs all compilation tasks including staging resources from both main and test
- jar - Generates a jar archive with all the compiled classes
- test - Runs the tests
- publish - Think Maven deploy
- publishToMavenLocal - Installs the project jar to your local maven cache (aka ~/.m2/repository). Note that Gradle never uses this, but it can be useful for testing your build with other local Maven-based builds.
- eclipse - Generates an Eclipse project
- idea - Generates an IntelliJ/IDEA project (although the preferred approach is to use IntelliJ's Gradle import).
- clean - Cleans the build directory