anchor.diff:  
       ./gradlew build
   
  +== 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
  +http://eclipse.org[Eclipse] when working with the code. We use the
  +http://eclipse.org/m2e/[m2eclipse] eclipse plugin for maven support. Other IDEs and tools
  +should also work without issue as long as they use Maven 3.3.3 or better.
   
  +== Contributing
  +
  +Spring Cloud is released under the non-restrictive Apache 2.0 license,
  +and follows a very standard Github development process, using Github
  +tracker for issues and merging pull requests into master. If you want
  +to contribute even something trivial please do not hesitate, but
  +follow the guidelines below.
  +
  +=== Sign the Contributor License Agreement
  +Before we accept a non-trivial patch or pull request we will need you to sign the
  +https://cla.pivotal.io/sign/spring[Contributor License Agreement].
  +Signing the contributor's agreement does not grant anyone commit rights to the main
  +repository, but it does mean that we can accept your contributions, and you will get an
  +author credit if we do.  Active contributors might be asked to join the core team, and
  +given the ability to merge pull requests.
  +
  +=== Code of Conduct
  +This project adheres to the Contributor Covenant link:/CODE_OF_CONDUCT.adoc[code of
  +conduct]. By participating, you  are expected to uphold this code. Please report
  +unacceptable behavior to spring-code-of-conduct@pivotal.io.
  +
  +=== Code Conventions and Housekeeping
  +None of these is essential for a pull request, but they will all help.  They can also be
  +added after the original pull request but before a merge.
  +
  +* Use the Spring Framework code format conventions. If you use Eclipse
  +  you can import formatter settings using the
  +  `eclipse-code-formatter.xml` file from the
  +  https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/master/spring-cloud-dependencies-parent/eclipse-code-formatter.xml[Spring
  +  Cloud Build] project. If using IntelliJ, you can use the
  +  http://plugins.jetbrains.com/plugin/6546[Eclipse Code Formatter
  +  Plugin] to import the same file.
  +* Make sure all new `.java` files to have a simple Javadoc class comment with at least an
  +  `@author` tag identifying you, and preferably at least a paragraph on what the class is
  +  for.
  +* Add the ASF license header comment to all new `.java` files (copy from existing files
  +  in the project)
  +* Add yourself as an `@author` to the .java files that you modify substantially (more
  +  than cosmetic changes).
  +* Add some Javadocs and, if you change the namespace, some XSD doc elements.
  +* A few unit tests would help a lot as well -- someone has to do it.
  +* If no-one else is using your branch, please rebase it against the current master (or
  +  other target branch in the main project).
  +* When writing a commit message please follow http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html[these conventions],
  +  if you are fixing an existing issue please add `Fixes gh-XXXX` at the end of the commit
  +  message (where XXXX is the issue number).
  +
  
positive.code:         return new BrokerApiVersion();
      }
  
  == Deploying your broker
  
  Follow the http://docs.cloudfoundry.org/services/managing-service-brokers.html[documentation] to register the broker to Cloud Foundry.
  
  === Build
  
  The project is built with Gradle. The https://docs.gradle.org/current/userguide/gradle_wrapper.html[Gradle wrapper] allows you to build the project on multiple platforms and even if you do not have Gradle installed; run it in place of the `gradle` command (as `./gradlew`) from the root of the main project directory.
  
  
negative.code: 
  === Service beans
  
  The Open Service Broker API has three main endpoint groupings: catalog management, service instance provisioning/deprovisioning, and service instance binding/unbinding. The broker will need to provide one Spring bean to provide the necessary functionality for each endpoint grouping.
  
  For catalog management, the framework provides a default implementation that requires the broker to just provide an implementation of a link:spring-cloud-open-service-broker/src/main/java/org/springframework/cloud/servicebroker/model/Catalog.java[`Catalog` bean]. To override this default, provide your own bean that implements the link:spring-cloud-open-service-broker/src/main/java/org/springframework/cloud/servicebroker/service/CatalogService.java[`CatalogService`] interface.
  
  For service instance provisioning/deprovisioning, provide a Spring bean that implements the link:spring-cloud-open-service-broker/src/main/java/org/springframework/cloud/servicebroker/service/ServiceInstanceService.java[`ServiceInstanceService`] interface. There is no default implementation provided.
  
  For service instance binding/unbinding, provide a Spring bean that implements the link:spring-cloud-open-service-broker/src/main/java/org/springframework/cloud/servicebroker/service/ServiceInstanceBindingService.java[`ServiceInstanceBindingService`] interface. If the service broker does not provide any bindable services, this bean can be omitted and a default implementation will be provided.
  
  === API version verification
  
  