DATACMNS-687 - Added section on dependency management to reference docs.

Added a dedicated dependencies.adoc that outlines the usage of the Spring Data release train BOM as well as the way one would customize the release train to be used with Spring Boot.

Also, we now explicitly list the Spring Framework version the release requires.

src/main/asciidoc/dependencies.adoc

@@ -0,0 +1,57 @@
+[[dependencies]]
+= Dependencies
+
+Due to different inception dates of individual Spring Data modules, most of them carry different major and minor version numbers. The easiest way to find compatible ones is by relying on the Spring Data Release Train BOM we ship with the compatible versions defined. In a Maven project you'd declare this dependency in the `<dependencyManagement />` section of your POM:
+
+.Using the Spring Data release train BOM
+====
+[source, xml]
+----
+<dependencyManagement>
+  <dependencies>
+    <dependency>
+      <groupId>org.springframework.data</groupId>
+      <artifactId>spring-data-releasetrain</artifactId>
+      <version>${release-train}</version>
+      <scope>import</scope>
+      <type>pom</type>
+    </dependency>
+  <dependencies>
+</dependencyManagement>
+----
+====
+
+The current release train version is {releasetrainVersion}. The train names are ascending alphabetically and currently available ones are listed https://github.com/spring-projects/spring-data-commons/wiki/Release-planning[here]. The version name follows the following pattern: `${name}-${release}` where release can be one of the following:
+
+* `BUILD-SNAPSHOT` - current snapshots
+* `M1`, `M2` etc. - milestones
+* `RC1`, `RC2` etc. - release candidates
+* `RELEASE` - GA release
+* `SR1`, `SR2` etc. - service releases
+
+A working example of using the BOMs can be found in our https://github.com/spring-projects/spring-data-examples/tree/master/bom[Spring Data examples repository].
+
+If that's in place declare the Spring Data modules you'd like to use without a version in the `<dependencies />` block.
+
+.Declaring a dependency to a Spring Data module
+====
+[source, xml]
+----
+<dependencies>
+  <dependency>
+    <groupId>org.springframework.data</groupId>
+    <artifactId>spring-data-jpa</artifactId>
+  </dependency>
+<dependencies>
+----
+====
+
+[[dependencies.spring-boot]]
+== Dependency management with Spring Boot
+
+Spring Boot already selects a very recent version of Spring Data modules for you. In case you want to upgrade to a newer version nonetheless, simply configure the property `spring-data-releasetrain.version` to the train name and iteration you'd like to use.
+
+[[dependencies.spring-framework]]
+== Spring Framework
+
+The current version of Spring Data modules require Spring Framework in version {springVersion} or better. The modules might also work with an older bugfix version of that minor version. However, using the most recent version within that generation is highly recommended.

src/main/asciidoc/index.adoc

@@ -17,6 +17,7 @@ include::preface.adoc[]
 = Reference documentation
 
 :leveloffset: +1
+include::dependencies.adoc[]
 include::repositories.adoc[]
 include::auditing.adoc[]
 :leveloffset: -1

src/main/asciidoc/preface.adoc

@@ -10,4 +10,4 @@ The Spring Data Commons project applies core Spring concepts to the development
 * Bugtracker - https://jira.spring.io/browse/DATACMNS
 * Release repository - https://repo.spring.io/libs-release
 * Milestone repository - https://repo.spring.io/libs-milestone
-* Snapshot repository - https://repo.spring.io/libs-snapshot
+* Snapshot repository - https://repo.spring.io/libs-snapshot

src/main/asciidoc/repository-query-return-types-reference.adoc

@@ -21,9 +21,9 @@ NOTE: Geospatial types like (`GeoResult`, `GeoResults`, `GeoPage`) are only avai
 |`Optional<T>`|A Java 8 or Guava `Optional`. Expects the query method to return one result at most. In case no result is found `Optional.empty()`/`Optional.absent()` is returned. More than one result will trigger an `IncorrectResultSizeDataAccessException`.
 |`Stream<T>`|A Java 8 `Stream`.
 |`Slice`|A sized chunk of data with information whether there is more data available. Requires a `Pageable` method parameter.
-|`Page<T>`|A Slice with additional information, e.g. the total number of results. Requires a `Pageable` method parameter.
+|`Page<T>`|A `Slice` with additional information, e.g. the total number of results. Requires a `Pageable` method parameter.
 |`GeoResult<T>`|A result entry with additional information, e.g. distance to a reference location.
-|`GeoResults<T>`|A list of GeoResult<T> with additional information, e.g. average distance to a reference location.
-|`GeoPage<T>`|A Page with GeoResult<T>, e.g. average distance to a reference location.
+|`GeoResults<T>`|A list of `GeoResult<T>` with additional information, e.g. average distance to a reference location.
+|`GeoPage<T>`|A `Page` with `GeoResult<T>`, e.g. average distance to a reference location.
 |===============