网站建设公司包括哪些方面,wordpress添加单页模板,沈阳网络教育,wordpress skype目录
一、SpringBoot的定义
二、Spring Boot 优点
三、创建一个springboot的项目
四、使用IDEA创建SpringBoot失败案例 一、SpringBoot的定义 Spring 的诞⽣是为了简化 Java 程序的开发的#xff0c;⽽ Spring Boot 的诞⽣是为了简化 Spring 程序开发的。 Spring Boot 翻…目录
一、SpringBoot的定义
二、Spring Boot 优点
三、创建一个springboot的项目
四、使用IDEA创建SpringBoot失败案例 一、SpringBoot的定义 Spring 的诞⽣是为了简化 Java 程序的开发的⽽ Spring Boot 的诞⽣是为了简化 Spring 程序开发的。 Spring Boot 翻译⼀下就是 Spring 脚⼿架就是为了快速开发 Spring 框架⽽诞⽣的 Spring Boot 项⽬的⼀大特点约定⼤于配置。较于Spring需要配置Bean的扫描路径而SpringBoot就不需要 二、Spring Boot 优点 快速集成框架Spring Boot 提供了启动添加依赖的功能⽤于秒级集成各种框架。内置运⾏容器⽆需配置 Tomcat 等 Web 容器直接运⾏和部署程序。快速部署项⽬⽆需外部容器即可启动并运⾏项⽬。可以完全抛弃繁琐的 XML使⽤注解和配置的⽅式进⾏开发。⽀持更多的监控的指标可以更好的了解项⽬的运⾏情况。 SpringBoot的核心 1、快速添加依赖 2、内置web容器 3、自动装配即SpringBoot自动构建复杂对象构建好的对象可以直接使用 三、创建一个springboot的项目 因为我们⽤的 Idea 社区版2021.3选择安装SpringBoot插件才能创建 Spring Boot 项目。 SpringBoot插件名字为 接下来开始正式创建SpringBoot项目 1、先选择file-new-project 2、选择Spring Initializr选择国外的默认配置源 3、添加项目的依赖 一般是Web项目所以我们勾选最基本的 Web选项选择SpringBoot Devtools用于实现热部署其他可以等用到的时候再添加。 Spring Boot Devtools实现热部署 LombokJava注解 Spring Web: 外部服务 SpringBoot版本选择后缀不带英文字母的稳定版本其中低版本的比较稳定 点击下一步命名自己项目的名字和保存地址点击finash等待项目的创建 开始进行启动类初始化右击 项目名选择“ Add Framework Support” 如果出现以下蓝色且右上角带有三角形则启动类初始化成功 点击运行启动类出现以下图形则说明一个SpringBoot项目已经构建完成 四、使用IDEA创建SpringBoot失败案例 由于SpringBoot版本可能与IDEA某些版本产生冲突导致无法创建成功失败的案例有如下几种 1、Maven缺少plugins和dependencies两个选项 2、Cannot resolve symbol springframework 错误异常 解决方法 1第一种方法删除Maven本地的配置文件重新配置国内阿里源在进行重新下载Maven进行加载 阿里源文件settings.xml如下 ?xml version1.0 encodingUTF-8?!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
License); you may not use this file except in compliance
with the License. You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
--!--| This is the configuration file for Maven. It can be specified at two levels:|| 1. User Level. This settings.xml file provides configuration for a single user,| and is normally provided in ${user.home}/.m2/settings.xml.|| NOTE: This location can be overridden with the CLI option:|| -s /path/to/user/settings.xml|| 2. Global Level. This settings.xml file provides configuration for all Maven| users on a machine (assuming theyre all using the same Maven| installation). Its normally provided in| ${maven.conf}/settings.xml.|| NOTE: This location can be overridden with the CLI option:|| -gs /path/to/global/settings.xml|| The sections in this sample file are intended to give you a running start at| getting the most out of your Maven installation. Where appropriate, the default| values (values used when the setting is not specified) are provided.||--
settings xmlnshttp://maven.apache.org/SETTINGS/1.0.0xmlns:xsihttp://www.w3.org/2001/XMLSchema-instancexsi:schemaLocationhttp://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd!-- localRepository| The path to the local repository maven will use to store artifacts.|| Default: ${user.home}/.m2/repositorylocalRepository/path/to/local/repo/localRepository--!-- interactiveMode| This will determine whether maven prompts you when it needs input. If set to false,| maven will use a sensible default value, perhaps based on some other setting, for| the parameter in question.|| Default: trueinteractiveModetrue/interactiveMode--!-- offline| Determines whether maven should attempt to connect to the network when executing a build.| This will have an effect on artifact downloads, artifact deployment, and others.|| Default: falseofflinefalse/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 to use for plugin lookup.pluginGroupcom.your.plugins/pluginGroup--/pluginGroups!-- proxies| This is a list of proxies which can be used on this machine to connect to the 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| Specification for one proxy, to be used in connecting to the network.|proxyidoptional/idactivetrue/activeprotocolhttp/protocolusernameproxyuser/usernamepasswordproxypass/passwordhostproxy.host.net/hostport80/portnonProxyHostslocal.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 to a remote server.|--servers!-- server| Specifies the authentication information to use when connecting to a particular server, identified by| a unique name within the system (referred to by the id attribute below).|| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are| used together.|serveriddeploymentRepo/idusernamerepouser/usernamepasswordrepopwd/password/server--!-- Another sample, using keys to authenticate.serveridsiteServer/idprivateKey/path/to/private/key/privateKeypassphraseoptional; leave empty if not used./passphrase/server--/servers!-- mirrors| This is a list of mirrors to be used in downloading artifacts from remote repositories.|| It works like this: a POM may declare a repository to use in resolving certain artifacts.| However, this repository may have problems with heavy traffic at times, so people have mirrored| it to several places.|| That repository definition will have a unique id, so we can create a mirror reference for that| repository, to be used as an alternate download site. The mirror site will be the preferred| server for that repository.|--mirrorsmirroridalimaven/idnamealiyun maven/nameurlhttp://maven.aliyun.com/nexus/content/groups/public//urlmirrorOfcentral/mirrorOf /mirror!-- mirror| Specifies a repository mirror site to use instead of a given repository. The repository that| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.|mirroridmirrorId/idmirrorOfrepositoryId/mirrorOfnameHuman Readable Name for this Mirror./nameurlhttp://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 to provide local machine-| specific paths and repository locations which allow the build to work in the local environment.|| For example, if you have an integration testing plugin - like cactus - that needs to know where| your Tomcat instance is installed, you can provide a variable here such that the variable is| dereferenced during the build process to configure 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 to specifying only artifact| repositories, plugin repositories, and free-form properties to be used as configuration| variables for plugins in the POM.||--profiles!-- profile| Specifies a set of introductions to the build process, to be activated using one or more of the| mechanisms described above. For inheritance purposes, and to activate profiles via activatedProfiles/| or the command line, profiles have to have an ID that is unique.|| An encouraged best practice for profile identification is to use 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 to understand what the set of introduced profiles is attempting| to accomplish, particularly when you only have a list of profile ids for debug.|| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.profileidjdk-1.4/idactivationjdk1.4/jdk/activationrepositoriesrepositoryidjdk14/idnameRepository for JDK 1.4 builds/nameurlhttp://www.myhost.com/maven/jdk14/urllayoutdefault/layoutsnapshotPolicyalways/snapshotPolicy/repository/repositories/profile--!--| Here is another profile, activated by the system property target-env with a value of dev,| which provides a specific path to the Tomcat instance. To use this, your plugin configuration| might hypothetically look like:|| ...| plugin| groupIdorg.myco.myplugins/groupId| artifactIdmyplugin/artifactId|| configuration| tomcatLocation${tomcatPath}/tomcatLocation| /configuration| /plugin| ...|| NOTE: If you just wanted to inject this configuration whenever someone set target-env to| anything, you could just leave off the value/ inside the activation-property.|profileidenv-dev/idactivationpropertynametarget-env/namevaluedev/value/property/activationpropertiestomcatPath/path/to/tomcat/instance/tomcatPath/properties/profile--/profiles!-- activeProfiles| List of profiles that are active for all builds.|activeProfilesactiveProfilealwaysActiveProfile/activeProfileactiveProfileanotherAlwaysActiveProfile/activeProfile/activeProfiles--
/settings2第二种方法创建一个空项目然后以新建模块的方式 创建新的SpringBoot项目 以这种方式没有感觉idea 版本和 maven版本存在冲突问题 接下来的步骤就和正常创建SpringBoot的步骤一模一样了完成以上全部步骤之后点击启动类运行如果能运行成功则SpringBoot项目就创建成功了。 异常案例若创建Maven时pom.xml文件为灰色没有变成蓝色时此时右键点击pom.xml文件再点击 add as maven project 稍等一会儿导入依赖就可以 说明 之所以没有配置Tomcat是因为Spring Boot内置了Tomcat 主要的几个代码介绍 1、SpringBootApplicationSpring Boot项目的核心注解主要目的是开启自动配置。 2、Configuration这是一个配置Spring的配置类 3、Controller标明这是一个Spring MVC的Controller控制器 4、main方法在main方法中启动一个应用即这个应用的入口
