配置maven仓库以及遇到的错误：Could not read settings.xml

最新推荐文章于 2022-10-14 20:31:43 发布
原创 最新推荐文章于 2022-10-14 20:31:43 发布 · 3.7k 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了Maven仓库的配置方法，默认仓库在C盘，可通过编辑Maven安装路径下conf里的settings.xml文件更改jar包存放路径，并在eclipse中添加该配置文件。还指出了Could not read settings.xml问题，可能是编码、空格及路径符号使用不当导致。

配置Maven仓库

maven的默认仓库是保存在 C:\Users\Administrator.m2\repository 目录下，即 jar 包存放路径，但是很多时候我们并不想把这些存在C盘想存在其他盘

步骤：

打开Maven的安装路径，找到 conf ，打开conf里面有个settings.xml 的文件，点击编辑，在里面添加一段代码，也就是你想把 jar 存放在哪，添加完之后保存

<localRepository>D:/eclipse/apache-maven-3.6.1/repo</localRepository>

在eclipse添加settings.xml配置文件：windows-preference-Maven里面的User-Settings
里面有一个是全局配置，一个是用户设置，把两个设置都改为你的settings路径就行了

Could not read settings.xml

Could not read settings.xml 字面上的意思是读取不了这个文件，说明你的文件里面的内容有问题
1、编码问题：内容里面最好不要有中文，配置完之后一定要以 utf-8 的形式保存
2、空格问题：允许换行，但是不允许有多个空格的出现
3、配置仓库路径的时候不要用的是 / 符号

<localRepository>D:/eclipse/apache-maven-3.6.1/repo</localRepository>

在这里插入图片描述

eclipse maven setting.xml
03-21
eclipse 集成maven 的配置文件 settings.xml ，配置了常用中央库镜像地址。只需配置本地仓库地址即可用。并对配置文件节点有中文说明
maven本地仓库错误jar包删除
01-24
一键删除maven本地仓库中下载错误的jar包资源(以lastUpdated结尾的文档)
eclipse使用mooctest插件时出现未在本机找到Maven配置
qq_51184727的博客
10-14 1425
eclipse使用mooctest插件时出现未在本机找到Maven配置
解决Maven提示：Could not read settings.xml, assuming default values
热门推荐
There is nothing
08-16 4万+
最近在学习Maven  时总是出现 Could not read settings.xml, assuming default values  错误，使得用户配置无法生效，在网上找了很多资料仍然解决不了，后来通过自己摸索找到了一下原因： ①：在  settings  配置文件中一定不能有中文，包括注释   内部也不能有。 ②：路径一定要写对：比如说  D:/Maven/repo/  中的路径
maven提示 Could not read settings.xml
悟世君子的博客
09-20 2万+
在Eclipse中配置maven时，提示错误：Could not read settings.xml 出错原因：maven的 settings.xml文件内有不合法字符，将其删除或修改正确即可 例如如下情况 只有一个 &lt;!--，就会报错，将其补全，即可 ...
Description Resource Path Location Type An error occurred while filtering resources TaskManagerWeb line 1 Maven Java EE Configuration Problem CoreException: Could not get the value for parameter compilerId for plugin execution default-compile: PluginResolutionException: Plugin org.apache.maven.plugins:maven-compiler-plugin:3.8.1 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-compiler-plugin:jar:3.8.1 -> org.apache.maven:maven-plugin-api:jar:3.0 -> org.sonatype.sisu:sisu-inject-plexus:jar:1.4.2 -> org.codehaus.plexus:plexus-component-annotations:jar:1.7.1: ArtifactDescriptorException: Failed to read artifact descriptor for org.codehaus.plexus:plexus-component-annotations:jar:1.7.1: UnresolvableModelException: Failure to transfer org.sonatype.forge:forge-parent:pom:10 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.sonatype.forge:forge-parent:pom:10 from/to central (https://repo.maven.apache.org/maven2): No connector factories available pom.xml /TaskManagerWeb line 63 Maven Project Build Lifecycle Mapping Problem CoreException: Could not get the value for parameter compilerId for plugin execution default-testCompile: PluginResolutionException: Plugin org.apache.maven.plugins:maven-compiler-plugin:3.8.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-core:jar:3.0, org.apache.maven:maven-settings:jar:3.0, org.apache.maven:maven-settings-builder:jar:3.0, org.apache.maven:maven-repository-metadata:jar:3.0, org.apache.maven:maven-model-builder:jar:3.0, org.apache.maven:maven-aether-provider:jar:3.0, org.sonatype.aether:aether-impl:jar:1.7, org.sonatype.aether:aether-spi:jar:1.7, org.sonatype.aether:aether-api:jar:1.7, org.sonatype.aether:aether-util:jar:1.7, org.codehaus.plexus:plexus-interpolation:jar:1.14, org.codehaus.plexus:plexus-classworlds:jar:2.2.3, org.codehaus.plexus:plexus-component-annotations:jar:1.7.1, org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3, org.sonatype.plexus:plexus-cipher:jar:1.4, org.apache.maven.shared:maven-shared-utils:jar:3.2.1, commons-io:commons-io:jar:2.5, org.apache.maven.shared:maven-shared-incremental:jar:1.1, org.codehaus.plexus:plexus-java:jar:0.9.10, org.codehaus.plexus:plexus-compiler-api:jar:2.8.4, org.codehaus.plexus:plexus-compiler-manager:jar:2.8.4, org.codehaus.plexus:plexus-compiler-javac:jar:2.8.4: Failure to transfer org.apache.maven:maven-core:jar:3.0 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven:maven-core:jar:3.0 from/to central (https://repo.maven.apache.org/maven2): The operation was cancelled. pom.xml /TaskManagerWeb line 63 Maven Project Build Lifecycle Mapping Problem Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (execution: default-compile, phase: compile) pom.xml /TaskManagerWeb line 63 Maven Project Build Lifecycle Mapping Problem Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (execution: default-testCompile, phase: test-compile) pom.xml /TaskManagerWeb line 63 Maven Project Build Lifecycle Mapping Problem Project configuration is not up-to-date with pom.xml. Select: Maven->Update Project... from the project context menu or use Quick Fix. TaskManagerWeb line 1 Maven Configuration Problem Project configurator "com.genuitec.eclipse.maven.wtp.hibernate.configurator.wtp" required by plugin execution "org.apache.maven.plugins:maven-war-plugin:3.2.3:war (execution: default-war, phase: package)" is not available. To enable full functionality, install the project configurator and run Maven->Update Project Configuration. pom.xml /TaskManagerWeb line 71 Maven Project Build Lifecycle Mapping Problem Project configurator "com.genuitec.eclipse.maven.wtp.spring.configurator.wtp" required by plugin execution "org.apache.maven.plugins:maven-war-plugin:3.2.3:war (execution: default-war, phase: package)" is not available. To enable full functionality, install the project configurator and run Maven->Update Project Configuration. pom.xml /TaskManagerWeb line 71 Maven Project Build Lifecycle Mapping Problem Unhandled exception type SQLException TaskController.java /TaskManagerWeb/src/main/java/com/taskmanager/controller line 57 Java Problem Unhandled exception type SQLException TaskController.java /TaskManagerWeb/src/main/java/com/taskmanager/controller line 69 Java Problem Unhandled exception type SQLException TaskController.java /TaskManagerWeb/src/main/java/com/taskmanager/controller line 80 Java Problem Unhan
05-30
另外，用户还提到maven-war-plugin3.2.3的configurator不可用，这可能是由于该插件的版本问题，或者配置错误。可能需要升级插件版本或检查配置是否正确。 接下来，我需要综合这些信息，给出具体的解决步骤。首先...
Errors occurred during the build. Errors running builder 'Maven Project Builder' on project 'ssmvcgfu'. Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6 Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6 Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6 Plugin
04-22
首先，检查Maven的settings.xml文件中的仓库配置是否正确。用户可能使用的是公司内部仓库，需要确认镜像设置和代理是否正常。引用[3]中提到了使用Maven命令生成项目时指定了archetype版本，可能需要正确的仓库访问...
MuleSoft在运行项目时提示如下错误，如何解决：[ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.10.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-compiler-plugin:jar:3.10.1: The following artifacts could not be resolved: org.apache.maven.plugins:maven-compiler-plugin:pom:3.10.1 (absent): Could not transfer artifact org.apache.maven.plugins:maven-compiler-plugin:pom:3.10.1 from/to mulesoft-releases (https://repository.mulesoft.org/releases/): Connection reset -> [Help 1]
最新发布
07-10
用户遇到的错误是关于maven-compiler-plugin无法解析，提示连接被重置。首先，我要理解这个错误的可能原因。 首先，错误信息显示Maven无法从MuleSoft的仓库下载插件的POM文件，连接被重置。这可能与网络问题有关，...
INFO] Scanning for projects... Downloading from alimaven: https://maven.aliyun.com/repository/public/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:2.5: Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5 Downloading from alimaven: https://maven.aliyun.com/repository/public/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-install-plugin:2.4: Plugin org.apache.maven.plugins:maven-install-plugin:2.4 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.4 Downloading from alimaven: https://maven.aliyun.com/repository/public/org/apa
05-09
当遇到 `org.apache.maven.plugins:maven-clean-plugin:2.5` 或其他插件无法正常下载的情况时，通常是因为本地配置错误或者远程仓库不可达引起的。以下是可能的原因以及解决方案： #### 1. 配置阿里云镜像源 如果...
maven提示 Could not read settings.xml
ifnotcorrect的博客
07-24 229
maven提示 Could not read settings.xml https://blog.csdn.net/wsjzzcbq/article/details/82788127 2018年09月20日 15:27:49 悟世君子 阅读数 3348 在Eclipse中配置maven时，提示错误：Could not read settings.xml 出错原因：maven的 set...
配置maven时提示：Could not read settings.xml
A_234_789的博客
03-10 688
一般这种情况都是你配置setting.xml文件时不小心有错误，只需要点击Browse再选择一次刚才选的setting.xml文件，就会弹出文件里的错误位置，如下 根据后面提示@22:6，即是文件的22行有问题，修改后即可。。 ...
解决Maven提示：Could not read settings.xml
07-21 483
在Eclipse中配置maven时，提示错误：Could not read settings.xml。用户配置无法生效。 1、首先检查自己的settings.xml配置文件，发现在<!---->中有配置中文的注释，把该注释去掉后可以进行保存。 2、 转载于:https://www.cnblogs.com/Jones-dd/p/9347090.html...
如何解决设置maven时Could not read settings.xml
huawangxin
06-13 2551
maven碰到了配置错误 错误信息: 解决方法: 可以看到再次点击Browse选择settings.xml文件后出现了警告：Unable to parse global ...\u7a9d\n<m... @226:3) , 这个226说明第226行出现了错误，导致了文件不能正常读取，仔细检查该行有没有错误或者中文信息。 更改后： 这个错误是settings.xml内标签配置有问题，替换正确的标签信息后能够解决。 放一下使用的路径配置：<localRepository&g...
maven配置setting.xml报Could not read settings.xml
zhou920786312的博客
08-02 1万+
Could not read settings.xml, assuming default values解决 1settings.xml不能有中文 2settings.xml 路径的标识是/
mvn 学习总结.不断更新中....
杨锋的blog
01-09 1045
1、下载maven版本：2.0.7下载地址：http://maven.apache.org/download.html2、安装mavenJDK：jdk1.52.1   解压缩maven-2.0.7-bin.zip 到你想安装的位置，如D:/software/。2.2 设置Maven系统环境变量，M2_HOME=D:/software/maven-2.0.7。2.3 添加Maven bin目录至系统
eclipse配置Maven Settings.xml文件报错：Could not read settings.xml
weixin_40601536的博客
05-06 8601
eclipse配置Maven Settings.xml文件报错：Could not read settings.xml 1.更新settings.xml文件后，重新加载settings.xml文件 2.报setting.xml文件107行有错误。 3.所以按下update Settings后，报Could not read settings.xml错误 4.打开setting.xml文件，发...
解决maven提示：Could not read settings.xml, assuming default values 错误
蓝缘
10-13 2万+
原因可能有两个： 1.settings.xml的格式有问题，（可以拿别来对照下） 2.有可能是repository仓库有问题。（路径最好不要有中文）
解决在Eclipse中配置maven时，提示错误：Could not read settings.xml的问题
S445708958的博客
07-25 1416
今天在Eclipse中配置maven的User Setting时，老是提示错误：Could not read settings.xml的问题，进过半天的网上查找，终于找到了解决办法： 1、配置标签之间可以换行但不可以有多余的空格，否则会报错 2、配置文件中不能有中文 ...
maven仓库错误
weixin_30467087的博客
03-09 221
1.jai_core 时间：2018年3月21日10:04:57 URL：https://mvnrepository.com/artifact/javax.media/jai_core/1.1.3 // https://mvnrepository.com/artifact/javax.media/jai_corecompile group: 'javax.media', name: 'jai...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值