$ cd spring-cloud-config-server -$ mvn spring-boot:run+$ ../mvnw spring-boot:run
diff --git a/vault/spring-cloud-config.html b/vault/spring-cloud-config.html index e2176230..d6f1ba27 100644 --- a/vault/spring-cloud-config.html +++ b/vault/spring-cloud-config.html @@ -474,7 +474,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
$ cd spring-cloud-config-server -$ mvn spring-boot:run+$ ../mvnw spring-boot:run
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
- <version>1.2.3.RELEASE</version>
+ <version>1.3.5.RELEASE</version>
<relativePath /> <!-- lookup parent from repository -->
</parent>
@@ -557,8 +557,8 @@ users. Example Maven configuration:
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
- <artifactId>spring-cloud-starter-parent</artifactId>
- <version>1.0.1.RELEASE</version>
+ <artifactId>spring-cloud-dependencies</artifactId>
+ <version>Brixton.RELEASE</version>
<type>pom</type>
<scope>import</scope>
</dependency>
@@ -784,7 +784,7 @@ Server? The strategy that governs this behaviour is the
{application} maps to "spring.application.name" on the client side;
-{profile} maps to "spring.active.profiles" on the client (comma separated list); and
+{profile} maps to "spring.profiles.active" on the client (comma separated list); and
{label} which is a server side feature labelling a "versioned" set of config files.
@@ -2040,7 +2040,7 @@ grabbing it in the bootstrap context and injecting one).