anchor.diff:  implement common patterns like single sign on, token relay and token
   exchange.
   
  +== Upgrading to 1.1.0
  +
  +Most of the OAuth2 features moved from this project to Spring Boot 1.3, so from version 1.1 things are a little different here. Here
  +is a guide to the available features as they were in 1.0, but with new names and slightly new APIs.
  +
  +As in 1.0, an app will activate `@EnableOAuth2Sso` if you bind provide some
  +following properties in the `Environment`.
  +
  +You can still customize the access rules in an SSO application, but instead
  +of a specific callback (the old `OAuth2SsoConfigurer`) all you do now is
  +add `@EnableOAuth2Sso` to a `WebSecurityConfigurerAdapter`.
  +For example if you want the resources under "/ui/**" to be protected with OAuth2:
  +
  +[source,java,indent=0]
  +----
  +	@Configuration
  +	@EnableOAuth2Sso
  +	@EnableAutoConfiguration
  +	protected static class TestConfiguration extends WebSecurityConfigurerAdapter {
  +		@Override
  +		public void match(RequestMatchers matchers) {
  +			matchers.antMatchers("/ui/**")
  +                .authorizeRequests().anyRequest().authenticated();
  +		}
  +	}
  +----
  +
  +In this case the rest of the application will default to the normal
  +Spring Boot access control for other paths (Basic authentication, or
  +whatever custom filters you put in place).
  +
  +There is no `@EnableOAuth2Resource` annotation in Spring Cloud 1.1.
  +You just use the regular `@EnableResourecServer` from Spring OAuth.
  +
   == Building
   
   :jdkversion: 1.7
   
   === Basic Compile and Test
   
  -To build the source you will need to install
  -http://maven.apache.org/run-maven/index.html[Apache Maven] v3.0.6 or above and JDK {jdkversion}.
  +To build the source you will need to install JDK {jdkversion}.
   
   Spring Cloud uses Maven for most build-related activities, and you
   should be able to get off the ground quite quickly by cloning the
   project you are interested in and typing
   
   ----
  -$ mvn install -s .settings.xml
  -----
  -
  -NOTE: You may need to increase the amount of memory available to Maven by setting
  -a `MAVEN_OPTS` environment variable with the value `-Xmx512m -XX:MaxPermSize=128m`
  -
  -The `.settings.xml` is only required the first time (or after updates
  -to dependencies). It is there to provide repository declarations so
  -that those do not need to be hard coded in the project poms.
  +$ ./mvnw install
  +----
  +
  +NOTE: You can also install Maven (>=3.3.3) yourself and run the `mvn` command
  +in place of `./mvnw` in the examples below. If you do that you also
  +might need to add `-P spring` if your local Maven settings do not
  +contain repository declarations for spring pre-release artifacts.
  +
  +NOTE: Be aware that you might need to increase the amount of memory
  +available to Maven by setting a `MAVEN_OPTS` environment variable with
  +a value like `-Xmx512m -XX:MaxPermSize=128m`. We try to cover this in
  +the `.mvn` configuration, so if you find you have to do it to make a
  +build succeed, please raise a ticket to get the settings added to
  +source control.
   
   For hints on how to build the project look in `.travis.yml` if there
   is one. There should be a "script" and maybe "install" command. Also
   look at the "services" section to see if any services need to be
   running locally (e.g. mongo or rabbit).  Ignore the git-related bits
  -that you might find in "before_install" since they will be able git
  +that you might find in "before_install" since they're related to setting git
   credentials and you already have those.
   
  -If you need mongo, rabbit or redis, see the README in the https://github.com/spring-cloud-samples/scripts[scripts
  -demo repository] for
  -instructions. For example consider using the "fig.yml" with
  -http://www.fig.sh/[Fig] to run them in Docker containers.
  +The projects that require middleware generally include a
  +`docker-compose.yml`, so consider using
  +http://compose.docker.io/[Docker Compose] to run the middeware servers
  +in Docker containers. See the README in the
  +https://github.com/spring-cloud-samples/scripts[scripts demo
  +repository] for specific instructions about the common cases of mongo,
  +rabbit and redis.
  +
  +NOTE: migration to the Maven wrapper (`.mvnw`) is underway. If you
  +find a project that doesn't have it yet, raise an issue to get it
  +added, and build with the command from `.travis.yml` (usually
  +`mvn install -s .settings.xml`).
   
   === Documentation
   
  
positive.code: 
  == Contributing
  
  Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like
  to contribute something, or simply want to hack on the code this document should help
  you get started.
  
  === Sign the Contributor License Agreement
  Before we accept a non-trivial patch or pull request we will need you to sign the
  
negative.code: any changes in the README it will then show up after a Maven build as
  a modified file in the correct place. Just commit it and push the change.
  
  === Working with the code
  If you don't have an IDE preference we would recommend that you use
  http://www.springsource.com/developer/sts[Spring Tools Suite] or
  