Add content for release trains
This commit is contained in:
@@ -1,11 +1,18 @@
|
||||
buildscript {
|
||||
dependencies {
|
||||
classpath "io.spring.gradle:dependency-management-plugin:0.4.0.RELEASE"
|
||||
}
|
||||
}
|
||||
|
||||
apply plugin: "io.spring.dependency-management"
|
||||
|
||||
dependencyManagement {
|
||||
imports {
|
||||
mavenBom '{@= groupId @}:{@= artifactId @}:{@= version @}'
|
||||
}
|
||||
}
|
||||
|
||||
dependencies {
|
||||
compile '{@= groupId @}:spring-cloud-spring-service-connector:{@= version @}'
|
||||
// If you intend to deploy the app on Cloud Foundry, add the following
|
||||
compile '{@= groupId @}:spring-cloud-cloudfoundry-connector:{@= version @}'
|
||||
|
||||
// If you intend to deploy the app on Heroku, add the following
|
||||
compile '{@= groupId @}:spring-cloud-heroku-connector:{@= version @}'
|
||||
|
||||
// It is okay to add more than one cloud connector; the right one will
|
||||
// be picked during runtime
|
||||
compile '{@= groupId @}:spring-cloud-starter-config'
|
||||
compile '{@= groupId @}:spring-cloud-starter-eureka'
|
||||
}
|
||||
@@ -1,21 +1,17 @@
|
||||
<dependencies>
|
||||
<parent>
|
||||
<groupId>{@= groupId @}</groupId>
|
||||
<artifactId>{@= artifactId @}</artifactId>
|
||||
<version>{@= version @}</version>
|
||||
</parent>
|
||||
<dependency>
|
||||
<groupId>{@= groupId @}</groupId>
|
||||
<artifactId>spring-cloud-spring-service-connector</artifactId>
|
||||
<artifactId>spring-cloud-starter-config</artifactId>
|
||||
<version>{@= version @}</version>
|
||||
</dependency>
|
||||
<!-- If you intend to deploy the app on Cloud Foundry, add the following -->
|
||||
<dependency>
|
||||
<groupId>{@= groupId @}</groupId>
|
||||
<artifactId>spring-cloud-cloudfoundry-connector</artifactId>
|
||||
<version>{@= version @}</version>
|
||||
</dependency>
|
||||
<!-- If you intend to deploy the app on Heroku, add the following -->
|
||||
<!-- It is okay to add more than one cloud connector; the right one will
|
||||
be picked during runtime -->
|
||||
<dependency>
|
||||
<groupId>{@= groupId @}</groupId>
|
||||
<artifactId>spring-cloud-heroku-connector</artifactId>
|
||||
<artifactId>spring-cloud-starter-eureka</artifactId>
|
||||
<version>{@= version @}</version>
|
||||
</dependency>
|
||||
</dependencies>
|
||||
|
||||
20
index.html
20
index.html
@@ -59,7 +59,7 @@ This app runs from the Spring Boot CLI (once the `spring-cloud-cli`
|
||||
extensions are installed), e.g.
|
||||
|
||||
```
|
||||
$ spring install org.springframework.cloud:spring-cloud-cli:1.0.0.BUILD-SNAPSHOT
|
||||
$ spring install org.springframework.cloud:spring-cloud-cli:1.0.3.RELEASE
|
||||
$ spring run configserver.groovy -- --server.port=8888
|
||||
```
|
||||
|
||||
@@ -84,6 +84,24 @@ results.
|
||||
[github.com](https://github.com) because that's where the default
|
||||
configuration repository lives.)
|
||||
|
||||
## Release Trains
|
||||
|
||||
Spring Cloud is an umbrella project consisting of independent projects with, in principle, different
|
||||
release cadences. To manage the protfolio a BOM (Bill of Materials) is published with a curated
|
||||
set of dependencies on the individual project (see below). The release trains have names, not
|
||||
versions, to avoid confusion with the sub-projects. The names are an alphabetic sequence (so
|
||||
you can sort them chronologically) with names of London Tube stations ("Angel" is the first
|
||||
release, "Brixton" is the second). When point releases of the individual projects accumulate to
|
||||
a critical mass, or if there is a critical bug in one of them that needs to be available to everyone,
|
||||
the release train will push out "service releases" with names ending ".SRX", where "X"
|
||||
is a number.
|
||||
|
||||
To use Spring Cloud in a traditional Java or Groovy project using
|
||||
Maven or Gradle, you can use the BOM only for dependency management or as a parent POM (Maven
|
||||
only). Example using the latest version:
|
||||
|
||||
{% include download_widget.md %}
|
||||
|
||||
## Features
|
||||
|
||||
Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.
|
||||
|
||||
Reference in New Issue
Block a user