Spring Boot项目的创建

hi 大家好,又见面了,今天继续讲解Spring Boot

文章目录

🐶1.什么是Spring Boot?

Spring 的诞⽣是为了简化 Java 程序的开发的，⽽ Spring Boot 的诞⽣是为了简化 Spring 程序开发的。
Spring Boot是基于Spring框架的一个轻量级开发框架，目的是让开发Spring应用变得更加简单快捷.
Spring Boot是Spring脚手架,就是为了快速开发 Spring 框架⽽诞⽣的
比如盖房子用脚手架让盖房子更高效哈哈~

🐶2.Spring Boot的优势

快速集成框架，Spring Boot 提供了启动添加依赖的功能，⽤于秒级集成各种框架。
内置运⾏容器，⽆需配置 Tomcat 等 Web 容器，直接运⾏和部署程序。
快速部署项⽬，⽆需外部容器即可启动并运⾏项⽬。
可以完全抛弃繁琐的 XML，使⽤注解和配置的⽅式进⾏开发。
⽀持更多的监控的指标，可以更好的了解项⽬的运⾏情况。

🐶3.Spring Boot项目创建

🌼3.1使用ieda创建

🥝3.1.1下载插件Spring Boot Helper

🥝3.1.2创建项目

添加依赖



第一次创建Spring Boot项目要加载很久,因为当前Spring Boot项目并没有在本地仓库,而且要保证在创建前配置了maven国内源,如果没有配置,下方为大家提供国内seetings.xml的信息

<?xml version="1.0" encoding="UTF-8"?><!--LicensedtotheApacheSoftwareFoundation(ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed withthis work for additional information
regarding copyright ownership.  TheASF licenses this file
toyou under the ApacheLicense,Version2.0(the
"License"); you may not use this file except in compliance
withtheLicense.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed toin writing,
software distributed under the License is distributed on an
"AS IS"BASIS,WITHOUTWARRANTIESORCONDITIONSOFANYKIND, either express or implied.  See the Licensefor the
specific language governing permissions and limitations
under the License.--><!--|This is the configuration file forMaven. It can be specified at two levels:||1.UserLevel. This settings.xml file providesconfigurationfor a single user,|                 and is normally provided in ${user.home}/.m2/settings.xml.||NOTE:This location can be overridden withtheCLI option:||-s /path/to/user/settings.xml
 ||2.GlobalLevel. This settings.xml file providesconfigurationfor all Maven|                 users on a machine (assuming they're all using the same Maven|                 installation).It's normally provided in
 |                 ${maven.conf}/settings.xml.||NOTE:This location can be overridden withtheCLI option:||-gs /path/to/global/settings.xml
 ||The sections in this sample file are intended togive you a running start at
 | getting the most out of your Maveninstallation. Where appropriate, the default| values (values used when the setting is not specified) are provided.||--><settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"><!-- localRepository
   |The path tothe local repository maven will use tostore artifacts.||Default: ${user.home}/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>--><!-- interactiveMode
   |This will determine whether maven prompts you when it needs input. If set tofalse,| maven will use a sensible default value, perhaps based on some other setting,for| the parameter in question.||Default:true<interactiveMode>true</interactiveMode>--><!-- offline
   |Determines whether maven should attempt toconnecttothe network when executing a build.|This will have an effect on artifact downloads, artifact deployment, and others.||Default:false<offline>false</offline>--><!-- pluginGroups
   |This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.| when invoking a command line like "mvn prefix:goal".Maven will automatically add the group identifiers
   |"org.apache.maven.plugins" and "org.codehaus.mojo"if these are not already contained in the list.|--><pluginGroups><!-- pluginGroup
     |Specifies a further group identifier tousefor plugin lookup.<pluginGroup>com.your.plugins</pluginGroup>--></pluginGroups><!-- proxies
   |This is a list of proxies which can be used on this machine toconnecttothe network.|Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.|--><proxies><!-- proxy
     |Specificationfor one proxy,tobe used in connecting tothe network.|<proxy><id>optional</id><active>true</active><protocol>http</protocol><username>proxyuser</username><password>proxypass</password><host>proxy.host.net</host><port>80</port><nonProxyHosts>local.net|some.host.com</nonProxyHosts></proxy>--></proxies><!-- servers
   |This is a list of authentication profiles, keyed by the server-id used within the system.|Authentication profiles can be used whenever maven must make a connection toa remote server.|--><servers><!-- server
     |Specifies the authentication information touse when connecting toa particular server, identified by
     | a unique name within the system (referred toby the 'id' attribute below).||NOTE:You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.|<server><id>deploymentRepo</id><username>repouser</username><password>repopwd</password></server>--><!--Another sample, using keys toauthenticate.<server><id>siteServer</id><privateKey>/path/to/private/key</privateKey><passphrase>optional; leave empty if not used.</passphrase></server>--></servers><!-- mirrors
   |This is a list of mirrors tobe used in downloading artifacts from remote repositories.||It works like this: a POM may declare a repository touse in resolving certain artifacts.|However,this repository may have problems withheavy traffic at times, so people have mirrored
   | it toseveral places.||That repository definition will have a unique id, so we can create a mirror reference for that
   | repository,tobe used as an alternate download site. The mirror site will be the preferred
   | server for that repository.|--><mirrors><mirror><id>alimaven</id><name>aliyun maven</name><url>http://maven.aliyun.com/nexus/content/groups/public/</url><mirrorOf>central</mirrorOf></mirror><!-- mirror
     |Specifies a repository mirror site touse instead of a given repository. The repository that
     |this mirror serves has an ID that matches the mirrorOf element of thismirror. IDs are used
     |for inheritance and direct lookup purposes, and must be unique across the set of mirrors.|<mirror><id>mirrorId</id><mirrorOf>repositoryId</mirrorOf><name>HumanReadableNameforthisMirror.</name><url>http://my.repository.com/repo/path</url></mirror>--></mirrors><!-- profiles
   |This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended toprovide local machine-| specific paths and repository locations which allow the build towork in the local environment.||For example,if you have an integration testing plugin - like cactus - that needs toknow where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process toconfigure the cactus plugin.||As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml)- will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.|Finally, the list of active profiles can be specified directly from the command line.||NOTE:For profiles defined in the settings.xml, you are restricted tospecifying only artifact
   |       repositories, plugin repositories, and free-form properties tobe used as configuration
   |       variables for plugins in the POM.||--><profiles><!-- profile
     |Specifies a set of introductions tothe build process,tobe activated using one or more of the
     | mechanisms described above. For inheritance purposes, and toactivate profiles via <activatedProfiles/>| or the command line, profiles have tohave an ID that is unique.||An encouraged best practice for profile identification is touse a consistent naming convention
     |for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.|This will make it more intuitive tounderstand what the set of introduced profiles is attempting
     |toaccomplish, particularly when you only have a list of profile id's for debug.||This profile example usestheJDK version totrigger activation, and providesaJDK-specific repo.<profile><id>jdk-1.4</id><activation><jdk>1.4</jdk></activation><repositories><repository><id>jdk14</id><name>RepositoryforJDK1.4 builds</name><url>http://www.myhost.com/maven/jdk14</url><layout>default</layout><snapshotPolicy>always</snapshotPolicy></repository></repositories></profile>--><!--|Here is another profile, activated by the system property 'target-env' witha value of 'dev',| which providesa specific path totheTomcatinstance. To use this, your plugin configuration
     | might hypothetically look like:||...|<plugin>|<groupId>org.myco.myplugins</groupId>|<artifactId>myplugin</artifactId>||<configuration>|<tomcatLocation>${tomcatPath}</tomcatLocation>|</configuration>|</plugin>|...||NOTE:If you just wanted toinjectthis configuration whenever someone set 'target-env' to|       anything, you could just leave off the <value/> inside the activation-property.|<profile><id>env-dev</id><activation><property><name>target-env</name><value>dev</value></property></activation><properties><tomcatPath>/path/to/tomcat/instance</tomcatPath></properties></profile>--></profiles><!-- activeProfiles
   |List of profiles that are active for all builds.|<activeProfiles><activeProfile>alwaysActiveProfile</activeProfile><activeProfile>anotherAlwaysActiveProfile</activeProfile></activeProfiles>--></settings>

这样就创建成功了!

🌼3.2使用网页创建

我们不仅可以采用idea创建spring boot项目,还可以采用网页创建
在浏览器搜索页面写入start.spring.io

创建成功了,然后在idea打开就好了
创建好之后要删除无用目录

🐶4.Spring Boot目录工程介绍

快速添加依赖的办法
使用edit starter插件



然后点击要添加的依赖,点击add即可添加依赖

🐶5.使用Spring Boot写一个最简单的程序

packagecom.example.demo;importorg.springframework.stereotype.Controller;importorg.springframework.web.bind.annotation.RequestMapping;importorg.springframework.web.bind.annotation.RestController;@RestController@RequestMapping("/user")publicclassUserController{@RequestMapping("/sayhi")publicStringsayHi(){return"Hi,Spring Boot.";}}

点击运行

Spring Boot设计思想是约定⼤于配置，类上标注
@SpringBootApplication 就可以启动 Spring Boot 项⽬
(下期解释约定大于配置👀)

🐶6.Spring Boot和Spring做对比

Spring Boot是基于Spring框架的一个轻量级开发框架，目的是让开发Spring应用变得更加简单快捷。Spring是一个完整的框架，包含了多个模块，如Spring MVC、Spring Security等，提供了广泛的功能支持。
Spring BootSpring开发难度Spring Boot简化了Spring应用的开发，不需要配置大量的XML文件，可以使用注解和自动配置。Spring需要使用XML和注解配置，需要更多的配置和代码编写。项目依赖Spring Boot提供了一个项目启动器（edit starter），包含了应用开发所需的常用依赖，可以快速构建应用Spring需要手动配置依赖，需要更多的时间和精力。应用测试Spring Boot支持嵌入式服务器，可以很方便地进行应用测试Spring需要手动启动服务器进行测试，比较复杂。性能Spring Boot在性能方面与Spring的表现相似，但Spring Boot可以更快地构建和运行应用。和Spring Boot 类似适用场景Spring Boot适合快速构建小型项目和原型应用Spring适合大型项目和需要更多功能支持的应用。
关于Spring Boot项目的创建和使用我们今天就讲解到这里,我们下期将继续深入学习它的其他知识,下期见咯😘