anchor.diff:  The generated eclipse projects can be imported by selecting `import existing projects`
   from the `file` menu.
   
  +
   == Contributing
   
   :spring-cloud-build-branch: master
   
  -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.
  +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.
  +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 https://github.com/spring-cloud/spring-cloud-build/blob/master/docs/src/main/asciidoc/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.
  +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
  -https://plugins.jetbrains.com/plugin/6546[Eclipse Code Formatter
  - Plugin] to import the same file.
  +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
  +  https://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).
  +  `@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 https://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).
  +* 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 https://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).
   
   === Checkstyle
   
  -Spring Cloud Build comes with a set of checkstyle rules.
  -You can find them in the `spring-cloud-build-tools` module.
  -The most notable files under the module are:
  +Spring Cloud Build comes with a set of checkstyle rules. You can find them in the `spring-cloud-build-tools` module. The most notable files under the module are:
   
   .spring-cloud-build-tools/
   ----
  
positive.code: 
  ==== Checkstyle configuration
  
  Checkstyle rules are *disabled by default*.
  To add checkstyle to your project just define the following properties and plugins.
  
  .pom.xml
  ----
  
negative.code: <5> Project style conventions for Intellij that apply most of Checkstyle rules
  
  .Code style
  
  image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/{spring-cloud-build-branch}/docs/src/main/asciidoc/images/intellij-code-style.png[Code style]
  
  Go to `File` -> `Settings` -> `Editor` -> `Code style`. There click on the icon next to the `Scheme` section. There, click on the `Import Scheme` value and pick the `Intellij IDEA code style XML` option. Import the `spring-cloud-build-tools/src/main/resources/intellij/Intellij_Spring_Boot_Java_Conventions.xml` file.
  
  .Inspection profiles
  
  image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/{spring-cloud-build-branch}/docs/src/main/asciidoc/images/intellij-inspections.png[Code style]
  
  Go to `File` -> `Settings` -> `Editor` -> `Inspections`. There click on the icon next to the `Profile` section. There, click on the `Import Profile` and import the `spring-cloud-build-tools/src/main/resources/intellij/Intellij_Project_Defaults.xml` file.
  
  .Checkstyle
  
  To have Intellij work with Checkstyle, you have to install the `Checkstyle` plugin. It's advisable to also install the `Assertions2Assertj` to automatically convert the JUnit assertions
  
  image::https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/{spring-cloud-build-branch}/docs/src/main/asciidoc/images/intellij-checkstyle.png[Checkstyle]
  
  Go to `File` -> `Settings` -> `Other settings` -> `Checkstyle`. There click on the `+` icon in the `Configuration file` section. There, you'll have to define where the checkstyle rules should be picked from. In the image above, we've picked the rules from the cloned Spring Cloud Build repository. However, you can point to the Spring Cloud Build's GitHub repository (e.g. for the `checkstyle.xml` : `https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/master/spring-cloud-build-tools/src/main/resources/checkstyle.xml`). We need to provide the following variables:
  
  - `checkstyle.header.file` - please point it to the Spring Cloud Build's, `spring-cloud-build-tools/src/main/resources/checkstyle-header.txt` file either in your cloned repo or via the `https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/master/spring-cloud-build-tools/src/main/resources/checkstyle-header.txt` URL.
  - `checkstyle.suppressions.file` - default suppressions. Please point it to the Spring Cloud Build's, `spring-cloud-build-tools/src/checkstyle/checkstyle-suppressions.xml` file either in your cloned repo or via the `https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/master/spring-cloud-build-tools/src/checkstyle/checkstyle-suppressions.xml` URL.
  - `checkstyle.additional.suppressions.file` - this variable corresponds to suppressions in your local project. E.g. you're working on `spring-cloud-contract`. Then point to the `project-root/src/checkstyle/checkstyle-suppressions.xml` folder. Example for `spring-cloud-contract` would be: `/home/username/spring-cloud-contract/src/checkstyle/checkstyle-suppressions.xml`.
  
  IMPORTANT: Remember to set the `Scan Scope` to `All sources` since we apply checkstyle rules for production and test sources.