Latest commit 9ee13be Jul 11, 2016 @olivergierke olivergierke #197 - Upgraded to Spring Boot 1.4 RC1.
Tweaked the output folder for Querydsl type generation to avoid running into a bug in the Maven compiler plugin 3.5.1 [0].

Fixed an issue in a sample script used to demonstrate MongoDB script execution as the new JavaScript engine seems to be more strict.

Switched to the MongoDB starter and excluded the legacy MongoDB Java driver from projects using Querydsl to consistently make use of the current driver only.

[0] https://issues.apache.org/jira/browse/MCOMPILER-271

README.adoc

Spring Data - Release Train BOM example

This project shows the usage of the Spring Data release train in a non-Spring-Boot project with both Maven and Gradle.

Properties

In both Maven and Gradle a couple of properties are used to define the versions of Spring Framework and Spring Data to use. For Spring Framework a plain version is used. For Spring Data we refer to a particular revision of a release train. The naming of Spring Data releases uses the following conventions:

  • ${release-train}-M1 → Milestones

  • ${release-train}-RC1 → Release candidate

  • ${release-train}-RELEASE → GA version

  • ${release-train}-SR1 → Services release (bugfixes) for that release train

Maven

The <dependencyManagement /> section declares dependencies to the BOMs for both Spring and Spring Data, using the import scope and pom type.

The standard <dependencies /> section can now list Spring Framework and Spring Data dependencies without declaring a version and still be sure all libraries are in matching versions.

Note, that we don’t declare a Spring Framework dependency here. The import of the Spring Framework BOM nonetheless makes sure we control the version of all transitive Spring Framework dependencies pulled in by the Spring Data modules.

Gradle

Gradle does not support Maven BOMs out of the box so the first thing to do is to declare a buildscript dependency on the dependency management plugin and apply it to the project.

With the plugin applied, the dependencyManagement section can be used to import the Spring Framework and Spring Data BOMs.

The standard dependencies section can now list Spring and Spring Data dependencies without declaring a version and still be sure all libraries are in matching versions.

Note, that we don’t declare a Spring Framework dependency here. The dependency management plugin and Spring Framework BOM nonetheless makes sure we control the version of all transitive Spring Framework dependencies pulled in by the Spring Data modules.