精华内容
下载资源
问答
  • IntelliJ IDEA新建SpringBoot项目报错Cannot resolve symbol问题症状问题频发人群几种原因附录一附录二附录三 问题症状 idea编译器报错: 1、【Cannot resolve symbol @springbootapplication】 2、【Cannot resolve...

    IntelliJ IDEA新建SpringBoot项目报错Cannot resolve symbol

    问题症状

    idea编译器报错:
    1、【Cannot resolve symbol @springbootapplication】
    2、【Cannot resolve symbol SpringApplication】

    问题频发人群

    一般在刚创建项目时会遇到该问题,特别是SpringBoot刚入门的小白(阿里镜像不知道怎么配、POM文件的书写规则也不是很清楚、Idea编译器也用的不熟悉),一脸懵逼就被挡在了入门之外,没有人指导的话很难入门,该问题常见于SpringBoot刚入门的小白

    几种原因

    1. 使用者依赖采用了Spring国外官网的依赖,没有采用阿里的依赖镜像(可看成是Spring官网的国内复制版本,阿里镜像被使用起来之后,项目加载依赖包速度更快)。

      解决方法: 找到Maven安装目录下\conf\settings.xml文件,并修改,详细修改方式见本文章附录一

    2. pom文件里面手动添加的依赖配置版本不一致或者配错了。

      解决方法: Dependence的写法是不固定的,复制artifactId标签的值“ spring-boot-starter-web ”到maven的官网去搜索对应的写法,详细步骤见本文章附录二

    3. Idea编译器的maven没有将依赖成功下载

      解决方法: 点击idea开发工具右侧栏的Maven,查看是否有标红的选项,有标红的选项则点击重新下载,等待依赖从镜像中全部下载完成,等到没有标红之后再去查看代码里面的注解是否还报错,如果依旧报错则选择File->Invaledate Caches/Restart清除缓存并重启idea,图文步骤见本文章附录三

    4. 以上这些步骤都做完了,还是不能解决一下啊星标处爆红的问题,可以采用下面这个方式:

      在这里插入图片描述

      解决方法: 将注释删掉重新写过,并重新选择依赖的包,我当时也是被这个问题坑了好久才发现。

    附录一

    step 1: 找到Maven安装目录下\conf\settings.xml文件。
    step 2: 替换为如下xml配置:

    <?xml version="1.0" encoding="UTF-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 at
    
        http://www.apache.org/licenses/LICENSE-2.0
    
    Unless 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 they're all using the same Maven
     |                 installation). It's normally provided in
     |                 ${maven.home}/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 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 to the local repository maven will use to store artifacts.
       |
       | Default: ${user.home}/.m2/repository
    	-->
      <localRepository>D:/MavenRep</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: true
      <interactiveMode>true</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: 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 to use for plugin lookup.
        <pluginGroup>com.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.
         |
        <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 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.
         |
        <server>
          <id>deploymentRepo</id>
          <username>repouser</username>
          <password>repopwd</password>
        </server>
        -->
    
        <!-- Another sample, using keys to authenticate.
        <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 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.
       |-->
      <mirrors>
        <!-- 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.
         |
        <mirror>
          <id>mirrorId</id>
          <mirrorOf>repositoryId</mirrorOf>
          <name>Human Readable Name for this Mirror.</name>
          <url>http://my.repository.com/repo/path</url>
        </mirror>
         -->
        <mirror>
            <id>nexus-aliyun</id>
            <mirrorOf>central</mirrorOf>
            <name>Nexus aliyun</name>
            <url>http://maven.aliyun.com/nexus/content/groups/public</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 id's for debug.
         |
         | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
        <profile>
          <id>jdk-1.4</id>
    
          <activation>
            <jdk>1.4</jdk>
          </activation>
    
          <repositories>
            <repository>
              <id>jdk14</id>
              <name>Repository for JDK 1.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' 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>
         |   <groupId>org.myco.myplugins</groupId>
         |   <artifactId>myplugin</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.
         |
        <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>
        -->
    	  <profile>
    			<id>jdk‐1.8</id>
    			<activation>
    			<activeByDefault>true</activeByDefault>
    			<jdk>1.8</jdk>
    			</activation>
    			<properties>
    			<maven.compiler.source>1.8</maven.compiler.source>
    			<maven.compiler.target>1.8</maven.compiler.target>
    			<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
    			</properties>
    		</profile>
      </profiles>
    
      <!-- activeProfiles
       | List of profiles that are active for all builds.
       |
      <activeProfiles>
        <activeProfile>alwaysActiveProfile</activeProfile>
        <activeProfile>anotherAlwaysActiveProfile</activeProfile>
      </activeProfiles>
      -->
    </settings>
    
    

    step 3 : 其中下面这部分需要替换为你自己定义的空目录,用以存放下载的依赖,我采用了自定义的目录(D:/MavenRep),如果不更改将会采用默认的目录(${user.home}/.m2/repository)。建议更换为自定义的目录。

     <!-- localRepository
       | The path to the local repository maven will use to store artifacts.
       |
       | Default: ${user.home}/.m2/repository
    	-->
      <localRepository>D:/MavenRep</localRepository>
    

    附录二

    step 1 : 手动添加的依赖配置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.langlangstudy</groupId>
        <artifactId>Spring-boot-01-helloworld</artifactId>
        <version>1.0-SNAPSHOT</version>
    
        <!-- Inherit defaults from Spring Boot -->
        <parent>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-parent</artifactId>
            <version>2.1.13.RELEASE</version>
        </parent>
        <dependencies>
            <!-- https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-starter-web -->
            <dependency>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-starter-web</artifactId>
                <version>2.1.13.RELEASE</version>
            </dependency>
        </dependencies>
        <!--这个插件,可以将应用打包成一个可执行的jar包-->
        <!-- https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-maven-plugin -->
        <build>
            <plugins>
                <plugin>
                    <groupId>org.springframework.boot</groupId>
                    <artifactId>spring-boot-maven-plugin</artifactId>
                    <version>2.1.13.RELEASE</version>
                </plugin>
            </plugins>
        </build>
    </project>
    

    step 2 : Dependence的写法是不固定的,复制artifactId标签值spring-boot-starter-web 到maven的官网https://mvnrepository.com/artifact/org.springframework.boot去搜索对应的写法,步骤如下:进入首页搜索对应的artifactId;
    001
    点击进入并选择版本;
    002
    003
    最后就拿到了相应版本的写法。
    004
    完成!

    附录三

    step 1 : 点击idea开发工具的右侧栏的Maven,查看2区域是否有标红的选项,有标红的选项则点击3区域的按钮重新下载,等待依赖从镜像中全部下载完成,等到没有标红之后再去查看代码里面的注解是否还报错;
    如果依旧报错则选择File– >Invaledate Caches/Restart清除缓存并重启idea。
    在这里插入图片描述

    展开全文
  • 新建springboot项目报错

    2018-05-20 20:07:29
    第一次建springboot项目总是报pom.xml里spring-boot-starter-parent找不到,查看本地仓库确实没有网上找到的资料都是没有解决方案,只好自己解决。可能是maven问题,jar包没有自动下载,于是重装了maven第二次启动...

    第一次建springboot项目总是报pom.xml里spring-boot-starter-parent找不到,

    查看本地仓库确实没有

    网上找到的资料都是没有解决方案,只好自己解决。

    可能是maven问题,jar包没有自动下载,于是重装了maven

    第二次启动还是报错,查看了本地仓库只有几兆,是网速太慢或者超时,于是删除掉项目重新下载

    看着是jar下下来了

    问题解决

    展开全文
  • 新建springboot项目报错:can’t resolve symbol ‘springbootApplication’ 错误截图如下: 应该是缺少jar包, 点击Maven Project---->install,结果如下,pom文件出错 解决方法: 对比了一下之前spring boot...

    新建springboot项目报错:can’t resolve symbol ‘springbootApplication’

    错误截图如下:

    在这里插入图片描述

    应该是缺少jar包,
    点击Maven Project---->install,结果如下,pom文件出错

    在这里插入图片描述

    解决方法:
    对比了一下之前spring boot项目的pom文件,发现是版本问题
    在这里插入图片描述
    然后我将2.2.6改为2.2.5,如上图所示,项目就好啦

    在这里插入图片描述

    展开全文
  • <dependency> <groupId>org.springframework.boot<...1.新搭建一个SpringBoot项目,在项目启动时直接报错Process finished with exit code 1” 后来才发现没有引用上面的jar包。此宝其实...
     
    <dependency>
       <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
      </dependency>

    1.新搭建一个SpringBoot项目,在项目启动时直接报错 Process finished with exit code 1”
    后来才发现没有引用上面的jar包。此宝其实是 添加classpath依赖。

    2.在新建项目的时候其实可以勾选此选项,当时忘记了勾选了 导致此问题发生,记录下。一般出这个问题大部分是因为maven的jar包引用问题或者有部分是idea工具问题

     

    展开全文
  • 解决: Server URL 改为: http://start.spring.io/
  • 我直接把地址改为https://start.aliyun.com/,一下子就出来了。
  • 就在今日,idea突然犯病,新建springboot报错,maven引入不进来各种报错 走过的坑: 刚开始报错:** Could not transfer artifact org.springframework.boot:spring-boot-starter-parent: pom:2.1.8.RELEASE from...
  • 跟着网上的教程第一次创建SpringBoot,创建好之后他们都可以直接写Controller类,然后运行就能从localhost访问hello word了。 但是我再第一次创建之后,出现下面的情况 Error:(3, 32) java: 程序包org.spring...
  • 每次创建spring项目,第一次成功,第二次再去创建就会报Error message: Cannot download 'https://start.spring.io': connect timed out这个错误,网上搜了一堆解决的方法,这里总结一下,总有一个能解决你的问题 ...
  • 新建springboot web项目,一建出来pom.xml就报错 错误的地方是这里: × <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>1.5.1.RELEASE...
  • 新建SpringBoot项目报错:org.springframework.context.ConfigurableApplicationContext cannot be resolved 解决方法是:通过cmd命令进入到dos系统,切换到springboot项目下,运行以下命令: mvn dependency:purge-...
  • 目录新建SpringBoot项目出错问题一、没有数据源二、找不到或无法加载主类三、在controller上使用@controller 无法注入到SpringBoot 新建SpringBoot项目出错问题 一、没有数据源 org.springframework.beans.factory....
  • 新建项目@SpringBootApplication报错 ** 入职一家新公司,接触springboot,当我在新建一个项目的时候回发现项目文件名旁边会出现一个红色感叹号,一直百度不到, 最后我考虑可看到org.springframework.boot....
  • springboot项目报错-The Bean Validation API is on the classpath but no implementation could be found 目录 文章目录***后记*** : 内容 新建简单的cxf整合springboot项目,但是控制台报错”The Bean ...
  • 新建springboot项目启动报错如下 Error starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled. 2018-09-13 15:43:37.061 ERROR 3056 — [ main] o.s.b...
  • idea新建springboot项目报错

    万次阅读 2019-02-26 23:05:31
    介绍关于“idea新建springboot项目报错”的一种情况,具体错误表现如下: 新建后maven下载依赖包很快就结束了。 打开默认的Application.java,可以看到提示报错,找不到spring的相关jar包。 2. 解决方法 方法1:...
  • intellij新建initilizr 项目 SpringBootApplication报错  BootApplication.java文件报错,找不到jarbao 这时候可以通过intellij的自动加载功能用maven来加入jar,加在了pom.xml中 实际上是pom.xml文件中加入了 ...
  • 新导入后,大部分代码都报错,这时候可以新建一个空白的springboot项目,后台自动下载依赖。 这时候还是有部分代码红的 可以点击右侧maven,点击刷新按钮重新加载。
  • 解决新建springboot项目启动报错问题

    千次阅读 2018-10-24 13:01:50
    2、清理项目缓存 //我这里用的是IDEA 点击File -> Invalidate caches -> Invalidate 3、清理8080端口 win + R 输入cmd 回车 netstat -ano | findstr 8080 回车 taskkill -pid 进程id -f 4...
  • eclipse新建springboot项目报错org.apache.maven.archiver.MavenArchiver.getManifest(pom文件第一行报错) eclipse提示:org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.Maven...
  • idea新建springboot项目pom文件报错

    千次阅读 2020-03-13 14:39:27
    前言 之前也有过类似的情况,只不过都是把spring-boot-starter-...新建springboot项目的问题 使用idea,一路next,到最后生成项目 然后pom文件报错 我特意换了一个全新的maven,发现是因为jar拉不下来,就配置了...
  • 由于新手今天用eclipse新建了一个springboot项目,但是...针对eclipse新建springboot项目pom文件报错问题&lt;parent&gt;……&lt;/parent&gt;标签报错maven update重新引入依赖 时间可能比较长,up...
  • 在deepin系统使用idea新建springboot项目,报Cannot resolve symbol 'SpringBootApplication’错误,在尝试了网上的各种办法均没有效果以后,将自定义的maven路径,改为默认之后,问题解决。 处理办法: 处理之前...
  • 当我们在新建springboot的时候会出现这样的报错信息,如图所示:我们可以这样解决 我们可以看一下之前的项目是怎么成功的,所以只需要把版本号更改一下即可修改为2.2.5即可。 然后右键项目,选择maven,选择update...
  • IDEA @SpringBootApplication报错原因【已经解决】

    万次阅读 热门讨论 2019-03-01 21:06:24
    新建项目后,项目的路径中会生成pom.xml文件和项目名.iml文件。新建项目后,IDEA不会自动刷新Maven的依赖。以Spring Application为例,新建项目编译时提示以下错误信息: java: 程序包org.springframework....

空空如也

空空如也

1 2 3 4 5 ... 19
收藏数 365
精华内容 146
关键字:

新建springboot项目报错

spring 订阅