Go to file
Steve Ebersole 59f498dc93 prepare 4.0.0.Beta2 2011-06-22 16:41:35 -05:00
buildSrc HHH-6036 - integration documentation generation 2011-03-29 15:14:09 -05:00
documentation HHH-5580 - Persisting entity name by default 2011-06-12 13:55:00 +02:00
etc HHH-6297 remove legacy cache api 2011-06-09 12:18:59 +08:00
gradle/wrapper HHH-6106 - Fix up IntelliJ project generation 2011-04-13 22:33:54 -05:00
hibernate-c3p0 HHH-6327 NPE when using JDBC connection pool C3pO 2011-06-17 16:43:33 +08:00
hibernate-core HHH-6348 POST_COMMIT_DELETE listener does not get executed 2011-06-22 17:45:59 +08:00
hibernate-ehcache HHH-6297 remove legacy cache api 2011-06-09 12:18:59 +08:00
hibernate-entitymanager typo in document 2011-06-20 12:17:56 +08:00
hibernate-envers HHH-6177: fixing a bug with mapping null references introduced by the last pull request 2011-06-22 08:42:13 +02:00
hibernate-infinispan HHH-6219 Nullify pending put map or singleton to avoid leaks 2011-06-07 12:16:21 +02:00
hibernate-proxool HHH-6098 - Slight naming changes in regards to new logging classes 2011-04-08 09:44:13 -05:00
hibernate-testing HHH-6297 remove legacy cache api 2011-06-09 12:18:59 +08:00
release HHH-6036 - integration documentation generation 2011-03-29 15:14:09 -05:00
.gitignore HHH-5942 - Migrate to JUnit 4 2011-03-14 13:14:07 -05:00
README.md some readme markdown improvements 2011-05-08 21:46:27 +02:00
build.gradle prepare 4.0.0.Beta2 2011-06-22 16:41:35 -05:00
changelog.txt prepare 4.0.0.Beta2 2011-06-22 16:41:35 -05:00
gradlew HHH-5897 - Upgrade to Gradle 0.9.2 2011-02-23 15:30:24 -06:00
gradlew.bat HHH-5897 - Upgrade to Gradle 0.9.2 2011-02-23 15:30:24 -06:00
hibernate_logo.gif SVN layout migration for core/trunk 2007-06-29 19:24:12 +00:00
lgpl.txt SVN layout migration for core/trunk 2007-06-29 19:24:18 +00:00
settings.gradle HHH-6036 integration documentation generation 2011-03-22 23:39:53 +08:00

README.md

How to build

Starting with development of version 4.0, Hibernate uses Gradle (http://gradle.org) as its build tool.

This README describes some of the basics developers and contributors new to Gradle need to know to get productive quickly.

Resources

To start with - here is a list of resources to obtain more information about Gradle:

Executing Tasks Across All Modules

To execute a task across all modules, simply perform that task from the root directory. Gradle will visit each subproject and execute that task if the subproject defines it.

Executing Tasks In Specific Module

To execute a task in a specific module you can either:

  1. cd into that module directory and execute the task
  2. 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

Common Java-module tasks

  • 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 hibernnate-entitymanager, Gradle would assemble and test hibernate-entitymanager as well as hibernate-envers (because envers depends on entitymanager)
  • classes - Compiles the main classes
  • testClasses - Compiles the test classes
  • jar - Generates a jar archive with all the compiled classes
  • test - Runs the tests
  • uploadArchives - Think Maven deploy
  • install - Installs the project jar to your local maven cache (aka ~/.m2/repository)
  • eclipse - Generates an Eclipse project
  • idea - Generates an IntelliJ/IDEA project.
  • clean - Cleans the build directory