$ git clone git@github.com:spring-cloud/spring-cloud-release-tools.git
+$ cd spring-cloud-release-tools
+$ ./mvnw clean install
+diff --git a/spring-cloud-release-tools.html b/spring-cloud-release-tools.html index 458539e2..e9f805c1 100644 --- a/spring-cloud-release-tools.html +++ b/spring-cloud-release-tools.html @@ -581,7 +581,15 @@ why this tool makes it easy to automate the release / dependency update process
Currently we only support running the Releaser to update the poms from Java
+Members of the Spring Cloud Team typically use this tool as follows. They first +clone the releaser locally and build the jar manually
+$ git clone git@github.com:spring-cloud/spring-cloud-release-tools.git
+$ cd spring-cloud-release-tools
+$ ./mvnw clean install
+Go to your project (e.g. Spring Cloud Sleuth)
@@ -590,8 +598,8 @@ why this tool makes it easy to automate the release / dependency update process$ git clone git@github.com:spring-cloud/spring-cloud-sleuth.git
$ cd spring-cloud-sleuth
-$ wget http://repo.spring.io/libs-milestone/org/springframework/cloud/internal/spring-cloud-release-tools-spring/1.0.0.M1/spring-cloud-release-tools-spring-1.0.0.M1.jar -O spring-cloud-release-tools-spring-1.0.0.M1.jar
-$ java -jar spring-cloud-release-tools-spring-1.0.0.M1.jar
+$ # example of running the releaser agains Dalston.SR1 tag
+$ java -jar ~/repo/spring-cloud-release-tools/spring-cloud-release-tools-spring/target/spring-cloud-release-tools-spring-*.jar --releaser.pom.branch=vDalston.SR1 --spring.config.name=releaser