2.3.1 由搭建项目基本框架开始

To begin, you’ll create a skeleton project for the licensing. You can either pull down the source code down from GitHub (https://github.com/carnellj/spmia-chapter2) or create a licensing-service project directory with the following directory structure:

我们先为授权微服务搭建一个基本框架。你可以从Github（https://github.com/carnellj/spmia-chapter2）上拉取源代码下来，或者也可以根据下面的目录结构创建授权微服务项目目录：

• licensing-service
• src/main/java/com/thoughtmechanix/licenses
• controllers
• model
• services
• resources

Once you’ve pulled down or created this directory structure, begin by writing your Maven script for the project. This will be the pom.xml file located at the root of the project directory. The following listing shows the Maven POM file for your licensing service.

拉取完代码或者创建完目录结构后，我们就开始编写项目的Maven脚本。这个脚本就是pom.xml文件，它位于项目目录的根目录。下面是授权微服务的Mavne POM文件的内容。

Listing 2.1 Maven pom file for the licensing service（清单2.1 授权微服务的Maven pom文件）

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.thoughtmechanix</groupId>
    <artifactId>licensing-service</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <packaging>jar</packaging>
    <name>EagleEye Licensing Service</name>
    <description>Licensing Service</description>
    <!--让Maven包含Spring Boot Starter依赖-->
    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>1.4.4.RELEASE</version>
        <relativePath/>
    </parent>
    <dependencies>
        <!--让Maven包含Spring Boot web依赖-->
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>
        <!--让Naven包含Spring Actuator依赖-->
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-actuator</artifactId>
        </dependency>
    </dependencies>
    <!--Note: Some the build properties and Docker build plugins have been
    excluded from the pom.xml in this pom (not in the source code in the
    github repository) because they are not relevant to our discussion here.
    注意：一些构建属性以及Docker构建插件从本pom.xml文件里排除了（本pom文件不在github代码库
    的源码里），因为它们与此处的讨论无关。
    -->
    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>
</project>

We won’t go through the entire script in detail, but note a few key areas as we begin. Spring Boot is broken into many individual projects. The philosophy is that you shouldn’t have to “pull down the world” if you aren’t going to use different pieces of Spring Boot in your application. This also allows the various Spring Boot projects to release new versions of code independently of one another. To help simplify the life of the developers, the Spring Boot team has gathered related dependent projects into various “starter” kits. In part 1 of the Maven POM you tell Maven that you need to pull down version 1.4.4 of the Spring Boot framework.

我们将不会深入探究整个脚本的细节，但有几个关键的地方要注意。Spring Boot分成了许多独立的项目。它的哲学理念是，如果你不准备在你的应用里使用Spring Boot的不同模块，那你就不应该将所有的模块都拉取下来。这样就使得不同的Spring Boot项目可以各自独立地发布新版本的代码。为了简化开发人员的工作，Spring Boot团队已经将相关的依赖项目整合进各种“starter”套件里。在Maven POM文件的第1部分里，我们告诉Maven我们需要拉取Spring Boot框架的1.4.4版本。

In parts 2 and 3 of the Maven file, you identify that you’re pulling down the Spring Web and Spring Actuator starter kits. These two projects are at the heart of almost any Spring Boot REST-based service. You’ll find that as you build more functionality into your services, the list of these dependent projects becomes longer.

在Maven文件的第2部分和第3部分里，我们指明了我们将拉取Spring Web和Spring Actuator starter套件。这两个starter是几乎所有基于REST的Spring Boot服务的核心。你将会发现，你在服务里构建越多的功能，这些依赖的清单会随着变得越长。

Also, Spring Source has provided Maven plugins that simplify the build and deployment of the Spring Boot applications. Step 4 tells your Maven build script to install the latest Spring Boot Maven plugin. This plugin contains a number of add-on tasks (such as spring-boot:run) that simplify your interaction between Maven and Spring Boot.

另外，Spring Source提供了一些Maven插件，这些插件简化了Spring Boot应用的构建和部署过程。第4步就是让Maven构建脚本安装最新的Spring Boot Maven插件。这个插件包含了一些附件任务（如spring-boot:run），它们简化了Maven和Spring Boot之间的交互。

Finally, you’ll see a comment that sections of the Maven file have been removed. For the sake of the trees, I didn’t include the Spotify Docker plugins in listing 2.1.

最后，你会看到一段注释，里面写着有些东西从Maven文件里移除了。为了与本书目录保持一致，我没有在清单2.1里包含Spotify Docker插件。

NOTE Every chapter in this book includes Docker files for building and deploying the application as Docker containers. You can find details of how to build these Docker images in the README.md file in the code sections of each chapter.

注意 本书的每个章节都会包含一个关于将应用构建并部署成Docker容器的Docker文件。你可以通过每个章节的README.md文件来了解关于如何构建这些镜像的细节。