Go to file
Hardy Ferentschik faca8f5dd4 HHH-8483 Deleting obsolte settings.gralde in metamodel-generator project and making sure artifact is correctly named in root level settings file 2013-11-12 16:07:00 +01:00
documentation HHH-8483 Adding creation of metamodelgen ascidoc to the build. Removing obsolete docbook files 2013-11-11 20:08:18 +08:00
etc HHH-6297 remove legacy cache api 2011-06-09 12:18:59 +08:00
gradle/wrapper HHH-8474 - Upgrade to Gradle 1.7 2013-09-06 10:54:08 -05:00
hibernate-c3p0 HHH-8499 - Prepare for 4.3 Beta4 release 2013-09-12 11:44:42 -05:00
hibernate-core HHH-2907 Adding @UpdateTimestamp generator annotation 2013-11-08 13:08:41 -06:00
hibernate-ehcache HHH-8619 - Account for "shadow" services as part of ServiceRegistry impls 2013-10-17 15:19:35 -05:00
hibernate-entitymanager HHH-8688 EntityGraph should add AttributeNode's for basic NamedAttributeNode 2013-11-08 09:59:04 -05:00
hibernate-envers HHH-8497 - Fix and test 2013-11-06 21:25:06 +01:00
hibernate-gradle-plugin HHH-8354 - New dirty-checking options based on bytecode enhancement 2013-10-09 13:00:10 -05:00
hibernate-infinispan HHH-8619 - Account for "shadow" services as part of ServiceRegistry impls 2013-10-17 15:19:35 -05:00
hibernate-maven-plugin HHH-8354 - New dirty-checking options based on bytecode enhancement 2013-10-09 13:00:10 -05:00
hibernate-osgi HHH-8646 use ServiceTracker in OsgiServiceUtil 2013-10-28 12:40:45 -04:00
hibernate-proxool HHH-8499 - Prepare for 4.3 Beta4 release 2013-09-12 11:44:42 -05:00
hibernate-testing HHH-7927 Enabling globally_quoted_identifiers breaks schema validation 2013-10-31 07:01:40 -04:00
release HHH-8483 Deleting obsolte settings.gralde in metamodel-generator project and making sure artifact is correctly named in root level settings file 2013-11-12 16:07:00 +01:00
shared HHH-8159 - Apply fixups indicated by analysis tools 2013-05-02 10:01:21 -05:00
tooling/metamodel-generator HHH-8483 Deleting obsolte settings.gralde in metamodel-generator project and making sure artifact is correctly named in root level settings file 2013-11-12 16:07:00 +01:00
.gitignore ignore target director from git 2013-11-11 20:54:24 +08:00
CONTRIBUTING.md Update CONTRIBUTING.md 2013-05-22 12:41:37 -05:00
README.md update README 2012-10-30 15:39:58 +08:00
build.gradle HHH-8483 Getting metamodel-generator:build working 2013-11-11 20:08:16 +08:00
changelog.txt 4.3.0.Beta5 release 2013-10-09 13:22:52 -05:00
gradlew HHH-8141 - Upgrade to Gradle 1.5 2013-04-04 13:01:39 -05:00
gradlew.bat HHH-8141 - Upgrade to Gradle 1.5 2013-04-04 13:01:39 -05: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
libraries.gradle HHH-8483 Getting metamodel-generator:build working 2013-11-11 20:08:16 +08:00
settings.gradle HHH-8483 Deleting obsolte settings.gralde in metamodel-generator project and making sure artifact is correctly named in root level settings file 2013-11-12 16:07:00 +01:00
utilities.gradle HHH-6736 - Support for SELECT ... FOR UPDATE SKIP LOCKED / read past locking 2013-02-20 09:31:14 -06:00

README.md

How to build

Starting with development of version 4.0, Hibernate uses Gradle as its build tool.

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

Quickstart

 git clone git://github.com/hibernate/hibernate-orm.git
 cd hibernate-orm
 ./gradlew clean build

If you are having problems with unresolved dependencies you need to configure access to the JBoss Nexus repository (see below).

Resources

General

JBoss Nexus

Gradle

Executing Tasks

Gradle uses the concept of build tasks (equivalent to Ant targets). You can get a list of available tasks via

gradle tasks

or if using gradle wrapper

./gradlew tasks

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
  • 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