anchor.diff:  
   = Code of Conduct
   
  -Please see our https://github.com/spring-projects/.github/blob/master/CODE_OF_CONDUCT.md[code of conduct]
  +Please see our https://github.com/spring-projects/.github/blob/master/CODE_OF_CONDUCT.md[code of conduct].
   
   = Similar but different
   
  -Each Spring module is slightly different than another in terms of team size, number of issues, etc. Therefore each project is managed slightly different. You will notice that this document is very similar to the https://github.com/spring-projects/spring-framework/wiki/Contributor-guidelines[Spring Framework Contributor guidelines]. However, there are some subtle differences between the two documents, so please be sure to read this document thoroughly.
  +Each Spring module is slightly different from others in terms of team size, number of issues, etc. Therefore, each project is managed slightly different. You will notice that this document is very similar to the https://github.com/spring-projects/spring-framework/wiki/Contributor-guidelines[Spring Framework Contributor guidelines]. However, there are some subtle differences between the two documents, so please be sure to read this document thoroughly.
   
   = Importing into IDE
   
   The following provides information on setting up a development environment that can run the sample in https://www.springsource.org/sts[Spring Tool Suite 3.6.0+]. Other IDE's should work using Gradle's IDE support, but have not been tested.
   
   * IDE Setup
  -* Install Spring Tool Suite 3.6.0+
  -* You will need the following plugins installed (can be found on the Extensions Page)
  - * Gradle Eclipse
  - * Groovy Eclipse
  +** Install Spring Tool Suite 3.6.0+
  +** You will need the following plugins installed (can be found on the Extensions Page)
  +*** Gradle Eclipse
  +*** Groovy Eclipse
   * Importing the project into Spring Tool Suite
  -* File-&gt;Import…-&gt;Gradle Project
  -
  -As of new versions of Spring Tool Suite, you might need to install Groovy Eclipse pointing directly to the updates plugin location. To install Groovy Eclipse on Spring Tool Suite based on Eclipse Oxigen you must do the following steps:
  -
  -Help-&gt;Install New Software…-&gt;Add the following URL into _Work with_ field:
  +** File -> Import… -> Gradle Project
  +
  +As of new versions of Spring Tool Suite, you might need to install Groovy Eclipse pointing directly to the updated plugin location. To install Groovy Eclipse on Spring Tool Suite based on Eclipse Oxigen you must do the following steps:
  +
  +Help -> Install New Software… -> Add the following URL into _Work with_ field:
   https://dist.springsource.org/snapshot/GRECLIPSE/e4.7/[https://dist.springsource.org/snapshot/GRECLIPSE/e4.7/]
   
   = Understand the basics
  
positive.code: 
  = Mind the whitespace
  
  Please carefully follow the whitespace and formatting conventions already present in the framework. 
  
  . Tabs, not spaces
  . Unix (LF), not dos (CRLF) line endings
  . Eliminate all trailing whitespace
  . Aim to wrap code at 120 characters, but favor readability over wrapping
  . Preserve existing formatting; i.e. do not reformat code for its own sake
  . Search the codebase using git grep and other tools to discover common naming conventions, etc.
  . UTF-8 encoding for Java sources and XML files
  
  Whitespace management tips
  
  . You can use the https://marketplace.eclipse.org/content/anyedit-tools[AnyEdit Eclipse plugin] to ensure spaces are used and to clean up trailing whitespaces.
  . Use git's pre-commit.sample hook to prevent invalid whitespace from being pushed out. You can enable it by moving ~/spring-security/.git/hooks/pre-commit.sample to ~/spring-security/.git/hooks/pre-commit and ensuring it is executable. For more information on hooks refer to https://git-scm.com/book/cs/ch7-3.html[Pro Git's Pre-Commit Hook's section]
  
  = Add Apache license header to all new classes
  
  = Update Apache license header to modified files as necessary
  
  Always check the date range in the license header. For example, if you've modified a file in 2012 whose header still reads
  <pre>
   * Copyright 2002-2011 the original author or authors.
  </pre>
  then be sure to update it to 2012 appropriately
  <pre>
   * Copyright 2002-2012 the original author or authors.
  </pre>
  
  = Use @since tags for newly-added public API types and methods
  
  e.g.
  <pre>
  /**
   * …
   *
   * @author First Last
   * @since 3.2
   * @see …
   */
  </pre>
  
  = Submit JUnit test cases for all behavior changes
  
  Search the codebase to find related unit tests and add additional `@Test` methods within. 
  
  . Any new tests should end in the name Tests (note this is plural). For example, a valid name would be `FilterChainProxyTests`. An invalid name would be `FilterChainProxyTest`.
  . New test methods should not start with test. This is an old JUnit3 convention and is not necessary since the method is annotated with @Test.
  
  = Update spring-security-x.y.rnc for schema changes
  
  
negative.code: 
  The Spring team takes a very conservative approach to accepting contributions to the framework. This is to keep code quality and stability as high as possible, and to keep complexity at a minimum. Your changes, if accepted, may be heavily modified prior to merging. You will retain "Author:" attribution for your Git commits granted that the bulk of your changes remain intact. You may be asked to rework the submission for style (as explained above) and/or substance. Again, we strongly recommend discussing any serious submissions with the Spring Framework team prior to engaging in serious development work.
  
  Note that you can always force push (`git push -f`) reworked / rebased commits against the branch used to submit your pull request. i.e. you do not need to issue a new pull request when asked to make changes.
  