Go to file
Lukasz Antoniak c7aa99d0d3 HHH-7187 - New Envers base test classes 2012-04-19 20:15:46 +08:00
buildSrc HHH-7197 rollback change of JdbcDirectoryProfile, seems that is a m9 feature 2012-03-26 17:55:11 +08:00
databases update postgresql testing profile 2012-04-10 11:15:08 +08:00
documentation doc typo 2012-04-11 17:08:47 +08:00
etc HHH-6297 remove legacy cache api 2011-06-09 12:18:59 +08:00
gradle/wrapper upgrade to use gradle 1.0 M8a 2012-02-28 16:47:34 +08:00
hibernate-c3p0 HHH-7193 2012-03-29 13:03:56 -05:00
hibernate-core Fix style and add credit where it is due 2012-04-18 18:11:47 +02:00
hibernate-ehcache HHH-7197 reimport imports 2012-03-26 16:17:45 +08:00
hibernate-entitymanager HHH-7197 reimport imports 2012-03-26 16:17:45 +08:00
hibernate-envers HHH-7187 - New Envers base test classes 2012-04-19 20:15:46 +08:00
hibernate-infinispan HHH-7256 Use minimalPuts in Infinispan 2012-04-17 19:50:37 +02:00
hibernate-proxool HHH-7197 reimport imports 2012-03-26 16:17:45 +08:00
hibernate-testing HHH-7187 - New Envers base test classes 2012-04-19 20:15:46 +08:00
release HHH-7197 - update build scripts to not use deprecated gradle apis and change manual's xml declation to use doc namespace 2012-03-26 15:12:10 +08:00
.gitignore HHH-5942 - Migrate to JUnit 4 2011-03-14 13:14:07 -05:00
README.md HHH-7208 - Fix Gradle links in README.md 2012-03-29 12:47:28 -05:00
build.gradle re-release 4.1.2 with 'Final' qualifier 2012-04-05 14:13:38 -05:00
changelog.txt release 4.1.2 2012-04-04 11:41:02 -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:

Here is the link of how to set up ~/.m2/settings.xml to use JBoss Nexus repo.

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