导入maven项目各个注解均报错的解决方案

更新时间:2023-04-04 08:43:51 阅读：评论：0

导入maven项目各个注解均报错

所遇问题

导入maven项目各个注解均报错了

思考1：

这个项目使用了springboot;spring是个”大容器”，所有对象的创建和管理都交给了它， (springboot是一个框架，一种全新的编程规范，他的产生简化了框架的使用，所谓简化是指简化了spring众多框架中所需的大量且繁琐的配置文件，所以 springboot是一个服务于框架的框架，服务范围是简化配置文件。

最明显的特点是，让文件配置变的相当简单、让应用部署变的简单（springboot内置服务器，并装备启动类代码），可以快速开启一个web容器进行开发。)；先去查看springboot是否扫描到这些文件；

结果：查看配置文件xml以及各层的依赖，应该没出错。

思考2：

该导入的包是否成功导入？查看maven依赖树（mvn dependency），并检查依赖版本等是否有用；结果：应该没错，依赖树上显示了加入的jar包。

思考3：

有事问度娘；百度上的方法各异；我并没有成功，也许是我操作或者对它们的理解出了问题吧；决定问大佬，我问了大佬，大佬从事安卓开发多年，所以帮我叫来另一个大佬；在另一个大佬的指点下，

解决方案

我先是去了本地仓库tting.xml下的镜像改为aliyun的镜像；（下图是查找你当前maven项目的本地仓库已经配置文件tting.xml的方法）

我这个是默认生成的，如果没有配置文件tting.xml;就自己新建一个；新建方法很多这里就不介绍了；附上我的tting.xml

<?xml version="1.0" encoding="utf-8"?><!--licend to the apache software foundation (asf) under oneor more contributor licen agreements.  e the notice filedistributed with this work for additional informationregarding copyright ownership.  the asf licens this fileto you under the apache licen, version 2.0 (the"licen"); you may not u this file except in compliancewith the licen.  you may obtain a copy of the licen athttp://www.apache.org/licens/licen-2.0unless required by applicable law or agreed to in writing,software distributed under the licen is distributed on an"as is" basis, without warranties or conditions of anykind, either express or implied.  e the licen for thespecific language governing permissions and limitationsunder the licen.--><!--| this is the configuration file for maven. it can be specified at two levels:||  1. ur level. this ttings.xml file provides configuration for a single|                 ur, and is normally provided in|                 ${ur.home}/.m2/ttings.xml.||                 note: this location can be overridden with the cli option:||                 -s /path/to/ur/ttings.xml||  2. global level. this ttings.xml file provides configuration for all|                 maven urs on a machine (assuming they're all using the|                 same maven installation). it's normally provided in|                 ${maven.home}/conf/ttings.xml.||                 note: this location can be overridden with the cli option:||                 -gs /path/to/global/ttings.xml|| the ctions 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 ud when the tting is not specified) are provided.||--><ttings xmlns="http://maven.apache.org/ttings/1.0.0"xmlns:xsi="http://www.w3.org/2001/xmlschema-instance"xsi:schemalocation="http://maven.apache.org/ttings/1.0.0 http://maven.apache.org/xsd/ttings-1.0.0.xsd"><!-- localrepository| the path to the local repository maven will u to store artifacts.|| default: ~/.m2/repository<localrepository>/path/to/local/repo</localrepository>--><!--<localrepository>c:/urs/administrator/.m2/repository</国庆趣事作文600字localrepository>  --><localrepository>f:/eclip_workspace20170314/repository</localrepository><!-- interactivemode| this will determine whether maven prompts you when it needs input. if t| to fal, maven will u a nsible default value, perhaps bad on some| other tting, 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: fal<offline>fal</offline>--><!-- plugingroups| this is a list of additional group identifiers that will be arched 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 the are not| already contained in the list.|--><plugingroups><!-- plugingroup| specifies a further group identifier to u for plugin lookup.<plugingroup>com.your.plugins</plugingroup>--></plugingroups><!-- proxies| this is a list of proxies which can be ud on this machine to connect to| the network. unless otherwi specified (by system property or command-| line switch), the first proxy specification in this list marked as active| will be ud.|--><proxies><!-- proxy| specification for one proxy, to be ud in connecting to the network.|<proxy><id>optional</id><active>true</active><protocol>http</protocol><urname>proxyur</urname><password>proxypass</password><host>proxy.host.net</host><port>80</port><nonproxyhosts>local.net|some.host.com</nonproxyhosts></proxy>--></proxies><!-- rvers| this is a list of authentication profiles, keyed by the rver-id ud| within the system. authentication profiles can be ud whenever maven must| make a connection to a remote rver.|--><rvers><!-- rver| specifies the authentication information to u when connecting to a| particular rver, identified by a unique name within the system| (referred to by the 'id' attribute below)健美操盘视频.|| note: you should either specify urname/password or|       privatekey/passphra, since the pairings are ud together.|<rver><id>deploymentrepo</id><urname>repour</urname><password>repopwd</password></rver>--><!-- another sample, using keys to authenticate.<rver><id>siterver</id><privatekey>/path/to/private/key</privatekey><passphra>optional; leave empty if not ud.</passphra></rver>--></rvers><!-- mirrors| this is a list of mirrors to be ud in downloading artifacts from remote| repositories.|| it works like this: a pom may declare a repository to u in resolving| certain artifacts. however, this repository may have problems with heavy| traffic at times, so people have mirrored it to veral places.|| that repository definition will have a unique id, so we can create a| mirror reference for that repository, to be ud as an alternate download| site. the mirror site will be the preferred rver for that repository.|--><mirrors><!-- mirror| specifies a repository mirror site to u instead of a given repository.| the repository that this mirror rves has an id that matches the| mirrorof element of this mirror. ids are ud for inheritance and direct| lookup purpos, and must be unique across the t of mirrors.|<mirror><id>mirrorid</id><mirrorof>repositoryid</mirrorof><name>human readable name for this mirror.</name><url>/d/file/titlepic/mirrorof><name>nexus aliyun</name><url>/d/file/titlepic/mirror><!-- profiles| this is a list of profiles which can be activat清明旅游好去处ed in a variety of ways,| and which can modify the build process. profiles provided in the| ttings.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 ction of this document (ttings.xml) - will be| discusd later. another way esntially 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 ttings.xml, you are restricted to|       specifying only artifact repositories, plugin repositories, and|       free-form properties to be ud as configuration variables for|       plugins in the pom.||--><profiles><!-- profile| specifies a t of introductions to the build process, to be activated| using one or more of the mechanisms described above. for inheritance| purpos, 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 u a| consistent naming convention for profiles, such as 'env-dev',| 'env-test', 'env-production', 'ur-jdcay', 'ur-brett', etc. this| will make it more intuitive to understand what the t 诗经 蒹葭of introduced| profiles is attempting to accomplish, particularly when you only have a| list of profile id's for debug.|| this profile example us 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 u this, your plugin configuration might hypotheti高清电脑桌面图片cally| 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|       t '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>--></ttings>

如何修改成aliyun镜像：

然后去本地仓库把.lastupdated为后缀的文件删除了；再重新下载依赖；也就那些jar包，解决了吗？并没有，再试一次？去本地仓库把.lastupdated为后缀的文件删除了，重新导入maven项目；不成啊。最后，我把本地仓库里的jar全删除了，再重新导入项目，重新下载依赖，就成功了。

原因：本地仓库里存有上一个项目所留下jar包，jar版本不同起了冲突，所以有一些jar无法使用，或者是导入项目后加载依赖时出现了jar包破损。（恳请纠正我，我也是百度并自己理解的出来的原因）

如果查看错误，出现不能被读或者它某jar也许是个zip文件这类错误，就是jdk版本太低，去更换一下项目的jdk环境，选择项目属性进行查看并更改