Spring Security（七）：2.4 Getting Spring Security
You can get hold of Spring Security in several ways. You can download a packaged distribution from the main Spring Security page, download individual jars from the Maven Central repository (or a Spring Maven repository for snapshot and milestone releases) or, alternatively, you can build the project from source yourself.
2.4.1 Usage with Maven (使用Maven)
A minimal Spring Security Maven set of dependencies typically looks like the following:
最小的Spring Security Maven依賴項通常如下所示： pom.xml<dependencies> <!-- ... other dependency elements ... --> <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-web</artifactId> <version>4.2.10.RELEASE</version> </dependency> <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-config</artifactId> <version>4.2.10.RELEASE</version> </dependency> </dependencies>
If you are using additional features like LDAP, OpenID, etc. you will need to also include the appropriate Section 2.4.3, “Project Modules”.
Maven Repositories
All GA releases (i.e. versions ending in .RELEASE) are deployed to Maven Central, so no additional Maven repositories need to be declared in your pom.
<repositories> <!-- ... possibly other repository elements ... --> <repository> <id>spring-snapshot</id> <name>Spring Snapshot Repository</name> <url>http://repo.spring.io/snapshot</url> </repository> </repositories>
If you are using a milestone or release candidate version, you will need to ensure you have the Spring Milestone repository defined as shown below:
如果您使用里程碑或候選釋出版本，則需要確保已定義Spring Milestone儲存庫，如下所示： pom.xml<repositories> <!-- ... possibly other repository elements ... --> <repository> <id>spring-milestone</id> <name>Spring Milestone Repository</name> <url>http://repo.spring.io/milestone</url> </repository> </repositories>
Spring Framework Bom (良好的spring框架)
Spring Security builds against Spring Framework 4.3.21.RELEASE, but should work with 4.0.x. The problem that many users will have is that Spring Security’s transitive dependencies resolve Spring Framework 4.3.21.RELEASE which can cause strange classpath problems.
Spring Security針對Spring Framework 4.3.21.RELEASE構建，但應該與4.0.x一起使用。許多使用者將遇到的問題是Spring Security的傳遞依賴性解決了Spring Framework 4.3.21.RELEASE，它可能導致奇怪的類路徑問題。 One (tedious) way to circumvent this issue would be to include all the Spring Framework modules in a <dependencyManagement> section of your pom. An alternative approach is to include thespring-framework-bomwithin your
<dependencyManagement> section of your
pom.xml as shown below:
解決此問題的一種（繁瑣）方法是將所有Spring Framework模組包含在pom的<dependencyManagement>部分中。另一種方法是將spring-framework-bom包含在pom.xml的<dependencyManagement>部分中，如下所示：
pom.xml
<dependencyManagement> <dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-framework-bom</artifactId> <version>4.3.21.RELEASE</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement>
This will ensure that all the transitive dependencies of Spring Security use the Spring 4.3.21.RELEASE modules.
這將確保Spring Security的所有傳遞依賴項都使用Spring 4.3.21.RELEASE模組。This approach uses Maven’s "bill of materials" (BOM) concept and is only available in Maven 2.0.9+. For additional details about how dependencies are resolved refer to Maven’s Introduction to the Dependency Mechanism documentation. 這種方法使用Maven的“物料清單”（BOM）概念，僅適用於Maven 2.0.9+。有關如何解析依賴關係的其他詳細資訊，請參閱Maven的依賴關係機制簡介文件。
2.4.2 Gradle
A minimal Spring Security Gradle set of dependencies typically looks like the following:
最小的Spring Security Gradle依賴項集通常如下所示： build.gradle.dependencies {
compile 'org.springframework.security:spring-security-web:4.2.10.RELEASE'
compile 'org.springframework.security:spring-security-config:4.2.10.RELEASE'
}
Gradle Repositories
All GA releases (i.e. versions ending in .RELEASE) are deployed to Maven Central, so using the mavenCentral() repository is sufficient for GA releases.
所有GA版本（即以.RELEASE結尾的版本）都部署到Maven Central，因此使用mavenCentral（）儲存庫足以支援GA版本。repositories {
mavenCentral()
}
If you are using a SNAPSHOT version, you will need to ensure you have the Spring Snapshot repository defined as shown below:
如果您使用的是SNAPSHOT版本，則需要確保定義了Spring Snapshot儲存庫，如下所示： build.gradle.repositories {
maven { url 'https://repo.spring.io/snapshot' }
}
If you are using a milestone or release candidate version, you will need to ensure you have the Spring Milestone repository defined as shown below:
如果您使用里程碑或候選釋出版本，則需要確保已定義Spring Milestone儲存庫，如下所示： build.gradle.repositories {
maven { url 'https://repo.spring.io/milestone' }
}
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 4.2.10.RELEASE with Spring Framework 4.3.21.RELEASE. However, at times there can be issues that come up so it is best to mitigate this using Gradle’s ResolutionStrategy as shown below:
預設情況下，Gradle將在解析傳遞版本時使用最新版本。這意味著在使用Spring Framework 4.3.21.RELEASE執行Spring Security 4.2.10.RELEASE時，通常不需要額外的工作。但是，有時可能會出現問題，因此最好使用Gradle的ResolutionStrategy來緩解這個問題，如下所示： build.gradle.configurations.all {
resolutionStrategy.eachDependency { DependencyResolveDetails details ->
if (details.requested.group == 'org.springframework') {
details.useVersion '4.3.21.RELEASE'
}
}
}
This will ensure that all the transitive dependencies of Spring Security use the Spring 4.3.21.RELEASE modules.
這將確保Spring Security的所有傳遞依賴項都使用Spring 4.3.21.RELEASE模組。 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. 此示例使用Gradle 1.9，但可能需要修改才能在Gradle的未來版本中使用，因為這是Gradle中的孵化功能。