anchor.diff:  	maven { url 'https://repo.spring.io/milestone' }
   }
   ----
  -
  -[[gradle-resolutionStrategy]]
  -=== Using Spring 4.0.x and Gradle
  -
  -By default Gradle will use the newest version when resolving transitive versions.
  -This means that often times no additional work is necessary when running Spring Security {spring-security-version} with Spring Framework {spring-version}.
  -However, at times there can be issues that come up so it is best to mitigate this using http://www.gradle.org/docs/current/dsl/org.gradle.api.artifacts.ResolutionStrategy.html[Gradle's ResolutionStrategy] as shown below:
  -
  -.build.gradle
  -[source,groovy]
  -[subs="verbatim,attributes"]
  -----
  -configurations.all {
  -	resolutionStrategy.eachDependency { DependencyResolveDetails details ->
  -		if (details.requested.group == 'org.springframework') {
  -			details.useVersion '{spring-version}'
  -		}
  -	}
  -}
  -----
  -
  -This will ensure that all the transitive dependencies of Spring Security use the Spring {spring-version} modules.
  -
  -NOTE: This example uses Gradle 1.9, but may need modifications to work in future versions of Gradle since this is an incubating feature within Gradle.
  
positive.code: 	<dependency>
  		<groupId>org.springframework.security</groupId>
  		<artifactId>spring-security-web</artifactId>
  		<version>{spring-security-version}</version>
  	</dependency>
  	<dependency>
  		<groupId>org.springframework.security</groupId>
  		<artifactId>spring-security-config</artifactId>
  		<version>{spring-security-version}</version>
  	</dependency>
  </dependencies>
  ----
  
  If you are using additional features like LDAP, OpenID, etc. you will need to also include the appropriate <<modules>>.
  
  [[maven-repositories]]
  === Maven Repositories
  
negative.code: 	<repository>
  		<id>spring-milestone</id>
  		<name>Spring Milestone Repository</name>
  		<url>https://repo.spring.io/milestone</url>
  	</repository>
  </repositories>
  ----
  
  
  [[gradle]]
  == Gradle
  
  Like most open source projects, Spring Security deploys its dependencies as Maven artifacts which allows for for first class Gradle support.
  The following sections provide details on how to consume Spring Security when using Gradle.
  
  === Spring Boot with Gradle
  
  Spring Boot provides a spring-boot-starter-security starter which aggregates Spring Security related dependencies together.
  The simplest and preferred method to leverage the starter is to use https://docs.spring.io/initializr/docs/current/reference/htmlsingle/[Spring Initializr] using an IDE integration (http://joshlong.com/jl/blogPost/tech_tip_geting_started_with_spring_boot.html[Eclipse], https://www.jetbrains.com/help/idea/spring-boot.html#d1489567e2[IntelliJ], https://github.com/AlexFalappa/nb-springboot/wiki/Quick-Tour[NetBeans]) or through https://start.spring.io.
  
  Alternatively, the starter can be added manually:
  
  .build.gradle
  [source,groovy]
  [subs="verbatim,attributes"]
  ----
  dependencies {
  	compile "org.springframework.boot:spring-boot-starter-security"
  }
  ----
  
  Since Spring Boot provides a Maven BOM to manage dependency versions, there is no need to specify a version.
  If you wish to override the Spring Security version, you may do so by providing a Gradle property:
  
  .build.gradle
  [source,groovy]
  [subs="verbatim,attributes"]
  ----
  ext['spring-security.version']='{spring-security-version}'
  ----
  
  Since Spring Security only makes breaking changes in major releases, it is safe to use a newer version of Spring Security with Spring Boot.
  However, at times it may be necessary to update the version of Spring Framework as well.
  This can easily be done by adding a Gradle property as well:
  
  .build.gradle
  [source,groovy]
  [subs="verbatim,attributes"]
  ----
  ext['spring.version']='{spring-version}'
  ----
  
  If you are using additional features like LDAP, OpenID, etc. you will need to also include the appropriate <<modules>>.
  
  === Gradle Without Spring Boot
  
  When using Spring Security without Spring Boot, the preferred way is to leverage Spring Security's BOM to ensure a consistent version of Spring Security is used throughout the entire project.
  This can be done by using the https://github.com/spring-gradle-plugins/dependency-management-plugin[Dependency Management Plugin].
  
  .build.gradle
  [source,groovy]
  [subs="verbatim,attributes"]
  ----
  plugins {
  	id "io.spring.dependency-management" version "1.0.6.RELEASE"
  }
  
  dependencyManagement {
  	imports {
  		mavenBom 'org.springframework.security:spring-security-bom:{spring-security-version}'
  	}
  }
  ----
  
  
  A minimal Spring Security Maven set of dependencies typically looks like the following:
  
  .build.gradle
  [source,groovy]
  [subs="verbatim,attributes"]
  ----
  dependencies {
  	compile "org.springframework.security:spring-security-web"
  	compile "org.springframework.security:spring-security-config"
  }
  ----
  
  If you are using additional features like LDAP, OpenID, etc. you will need to also include the appropriate <<modules>>.
  
  Spring Security builds against Spring Framework {spring-version}, but should generally work with any newer version of Spring Framework 5.x
  The problem that many users will have is that Spring Security's transitive dependencies resolve Spring Framework {spring-version} which can cause strange classpath problems.
  The easiest way to resolve this is to use the `spring-framework-bom` within your `<dependencyManagement>` section of your `pom.xml` as shown below:
  This can be done by using the https://github.com/spring-gradle-plugins/dependency-management-plugin[Dependency Management Plugin].
  
  .build.gradle
  [source,groovy]
  [subs="verbatim,attributes"]
  ----
  plugins {
  	id "io.spring.dependency-management" version "1.0.6.RELEASE"
  }
  
  dependencyManagement {
  	imports {
  		mavenBom 'org.springframework:spring-framework-bom:{spring-version}'
  	}
  }
  ----
  
  This will ensure that all the transitive dependencies of Spring Security use the Spring {spring-version} modules.
  
  [[gradle-repositories]]
  === Gradle Repositories
  