jpa-schema-gradle-plugin

Gradle plugin for generate schema or DDL scripts from JPA entities using JPA 2.1 schema generator. for Maven, see Maven Plugin.

Currently support EclipseLink (Reference Implementation) and Hibernate.

Before Announce...

READ MY LIP; JPA DDL GENERATOR IS NOT SILVER BULLET

Sometimes (most times exactly :P) JPA will generate weird scripts so you SHOULD modify them properly.

Version History

See Releases for more informations...

6.x (in progress...)

• Required JDK 8 or above.
• Required Gradle 6.0 or above. (for support Java 13 or above)

4.x

0.3.6

• Required Gradle 4.10 or above. (for support spring-boot plugin version 2.0+)

0.3

• Required Gradle 4.0 or above.
• Java 9 support.
• Required JDK 8 or above.
• No more output.resourcesDir = output.classesDir needed.
• No more buildscript dependencies needed.
• Dropped support DataNucleus, it was my mistake.
• Required Gradle 6.0 or above. (for support Java 13)

Reworking on 0.3

• Minimized spring dependency, only include spring-orm, spring-context, spring-aspects and its dependencies. (based on spring 5.x)
• Direct including any JPA implementation is removed, remains JUST API.
• Will improve test with each major release version of each JPA providers.
• Re-implemented with Kotlin, on my self-training.

If you have discussions, please make issue. discussions are always welcome.

How-to Use

see Gradle Plugins Registry.

plugins {
  id 'io.github.divinespear.jpa-schema-generate' version '0.3.6'
}

generateSchema {
  // default options
  // see SchemaGenerationConfig to all options
  ...
  // if you want multiple output
  targets {
    targetName {
      // same as default options
      ...
    }
  }
}

To generate schema, run

gradle generateSchema

or

./gradlew generateSchema

see also test cases Generate*Spec.groovy, as examples.

without persistence.xml

You MUST specify two options: vendor and packageToScan.

generateSchema {
  vendor = 'hibernate' // 'eclipselink', 'hibernate', or 'hibernate+spring'.
                       // you can use class name too. (like 'org.hibernate.jpa.HibernatePersistenceProvider')
  packageToScan = [ 'your.package.to.scan', ... ]
  ...
}

Plugin only dependencies

Since 0.3.4, you can add dependencies for plugin with configuration generateSchema.

// no need to add 'generateSchema' into configurations block.

dependencies {
  ...
  implementation 'org.springframework.boot:spring-boot-starter-data-jpa'
  // only need to load java.time converter from spring-data-jpa on schema generation
  generateSchema 'org.threeten:threetenbp:1.3.6'
}

generateSchema {
  ...  
  packageToScan = [
    // load java.time converter from spring-data-jpa
    'org.springframework.data.jpa.convert.threeten',
    'your.package.to.scan',
    ...
  ]
  ...
}

Provider specific

EclipseLink

• EclipseLink 2.5 on Java 9 without persistence.xml will not work.
• EclipseLink 2.6 on Java 12 or higher will not work. embedded ASM library cannot read class files.
• EclipseLink's Oracle{8,9,10,11}Platform uses some type classes from Oracle's JDBC driver. you should have it in your dependency.

Hibernate

• After 5.2, just use hibernate-core instead hibernate-entitymanager, it is merged.

• Naming strategy property is

  • 4.x: hibernate.ejb.naming_strategy
  • 5.x: hibernate.physical_naming_strategy / hibernate.implicit_naming_strategy

• For select dialect, do one of

  • set hibernate.dialect on properties
  • set databaseProductName, databaseMajorVersion, and/or databaseMinorVersion for determine dialect.

Hibernate with Spring ORM

• vendor should be hibernate+spring. (without persistence.xml)
• use io.spring.dependency-management for version management.
  • You can change hibernate version with hibernate.version property.

SchemaGenerationConfig

Here is full list of parameters of generateSchema.

How-to config library specific properties

It's just groovy map, so you can config like this:

generateSchema {
  ...
  // global properties
  properties = [
    'hibernate.dialect': 'org.hibernate.dialect.MySQL5InnoDBDialect',
    ...
  ]
  // you can set target-specific too.
  ...
}

Database Product Names

It's about databaseProductName property. If not listed below, will work as basic standard SQL.

for EclipseLink

databaseMajorVersion and databaseMinorVersion is not required.

• Oracle12 = Oracle 12c
• Oracle11 = Oracle 11g
• Oracle10 = Oracle 10g
• Oracle9 = Oracle 9i
• Oracle = Oracle with default compatibility
• Microsoft SQL Server
• DB2
• MySQL
• PostgreSQL
• SQL Anywhere
• Sybase SQL Server
• Adaptive Server Enterprise = Sybase
• Pointbase
• Informix Dynamic Server
• Firebird
• ingres
• Apache Derby
• H2
• HSQL Database Engine

for Hibernate

• All dialect list of 5.4.12
• Preregistered dialects of 5.4.12

For other versions, select tag to your version.

License

Source Copyright © 2013-2018 Sin Young "Divinespear" Kang (divinespear at gmail dot com). Distributed under the Apache License, Version 2.0.