I. Overview
This section also evolves using a single project, involving the main techniques of the most commonly used Springcloud section.
Two. Description of the environment
This time using the sprinboot1.5.9 version, the other Springcloud section uses the D5 version.
<parent> <groupId>org.springframework.boot</groupId> <artifactid>spring-boo t-starter-parent</artifactid> <version>1.5 . 9 . release</version> </parent> <dependencyManagement> <dependencies> <depe Ndency> <groupId>org.springframework.cloud</groupId> <artifactid>spring -cloud-dependencies</artifactid> <version>Dalston.SR5</version> <TYPE&G t;pom</type> <scope>import</scope> </dependency> </dependencie S> </dependencymanagement>
<build> <plugins> <plugin> <groupid>org.apache.maven.plugins</groupid > <artifactId>maven-compiler-plugin</artifactId> <configuration> <target >1.8</target> <version>1.8</version> </configuration> </plugin> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build>
The above is the first MAVEN plugin to be used, and additional plug-in content will need to be added later in the evolution process.
Three. Project structure
For example, it is the initial project structure. "
The parent of our POM project helps to complete the aggregation work of the project.
Now the original module is just a service provider Cloud-provider and a service consumer Cloud-consumer. [That Eureka is one of the things we started learning about, the service center].
001 Construction of the environment