maven提示 Could not read settings.xml

最新推荐文章于 2022-10-14 21:39:04 发布
最新推荐文章于 2022-10-14 21:39:04 发布
阅读量2.2w 收藏 8
点赞数 12
CC 4.0 BY-SA版权
分类专栏： maven
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/wsjzzcbq/article/details/82788127
本文解决在Eclipse中配置Maven时遇到的Could not read settings.xml错误，详细介绍了错误的原因及如何通过检查和修正settings.xml文件中的非法字符来解决问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

在Eclipse中配置maven时，提示错误：Could not read settings.xml
在这里插入图片描述
出错原因：maven的 settings.xml文件内有不合法字符，将其删除或修改正确即可

例如如下情况
在这里插入图片描述
只有一个 <!--，就会报错，将其补全，即可
在这里插入图片描述
在这里插入图片描述

DataX实战之MongoDB导入数据到mysql——打包jar包时出现Could not find goal assembly in plugin org.apache.maven.plugins
天冬忘忧的博客
09-07 1002
DataX实战之MongoDB导入数据到mysql——打包jar包时，出现Could not find goal assembly in plugin org.apache.maven.plugins报错的解决方案
maven settings.xml 配置文件
11-28
这是maven 自定义仓库配置方案。本地仓库默认放在C盘，如果要想将本地仓库转移到指定到自动以的位置，就需要配置setting.xml，下载后只需修改本地仓库的配置即可！
eclipse maven setting.xml
03-21
eclipse 集成maven 的配置文件 settings.xml ，配置了常用中央库镜像地址。只需配置本地仓库地址即可用。并对配置文件节点有中文说明
解决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/  中的路径
解决在Eclipse中配置maven时，提示错误：Could not read settings.xml的问题
S445708958的博客
07-25 1410
今天在Eclipse中配置maven的User Setting时，老是提示错误：Could not read settings.xml的问题，进过半天的网上查找，终于找到了解决办法： 1、配置标签之间可以换行但不可以有多余的空格，否则会报错 2、配置文件中不能有中文 ...
配置maven仓库以及遇到的错误：Could not read settings.xml
Woo_home的博客
05-19 3770
配置Maven仓库 maven的默认仓库是保存在 C:\Users\Administrator.m2\repository 目录下，即 jar 包存放路径，但是很多时候我们并不想把这些存在C盘想存在其他盘 步骤： 打开Maven的安装路径，找到 conf ，打开conf里面有个settings.xml 的文件，点击编辑，在里面添加一段代码，也就是你想把 jar 存放在哪，添加完之后保存 <l...
解决Maven提示：Could not read settings.xml
07-21 478
在Eclipse中配置maven时，提示错误：Could not read settings.xml。用户配置无法生效。 1、首先检查自己的settings.xml配置文件，发现在<!---->中有配置中文的注释，把该注释去掉后可以进行保存。 2、 转载于:https://www.cnblogs.com/Jones-dd/p/9347090.html...
C:\Users\26255>mvn help:system [WARNING] [WARNING] Some problems were encountered while building the effective settings [WARNING] Unrecognised tag: 'blocked' (position: START_TAG seen ...</url>\n <blocked>... @160:16) @ D:\tool\maven\apache-maven-3.6.1\bin\..\conf\settings.xml, line 160, column 16 [WARNING] [ERROR] Could not create local repository at E:\Maven\apache-maven-3.9.9\repo -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LocalRepositoryNotAccessibleException
最新发布
07-07
- 全局配置：Maven安装目录下的`conf/settings.xml`（例如：`E:\maven\maven-3.9.9\conf\settings.xml`） - 用户配置：用户目录下的`.m2/settings.xml`（例如：`C:\Users\Eric1\.m2\settings.xml`） 4. **无法创建...
C:\Users\z84405515\.jdks\ms-17.0.15\bin\java.exe -Dmaven.multiModuleProjectDirectory=C:\Users\z84405515\AppData\Local\Temp\archetype1tmp "-Dmaven.home=C:\Program Files\Maven" "-Dclassworlds.conf=C:\Program Files\Maven\bin\m2.conf" "-Dmaven.ext.class.path=C:\Program Files\JetBrains\IntelliJ IDEA 2024.3.2.2\plugins\maven\lib\maven-event-listener.jar" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2024.3.2.2\lib\idea_rt.jar=63111:C:\Program Files\JetBrains\IntelliJ IDEA 2024.3.2.2\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program Files\Maven\boot\plexus-classworlds-2.5.2.jar" org.codehaus.classworlds.Launcher -Didea.version=2024.3.2.2 -s "C:\Program Files\Maven\conf\settings.xml" -Dmaven.repo.local=C:\04_DevTools\maven_repo2 -DinteractiveMode=false -DgroupId=com.example -DartifactId=SpringBoot2 -Dversion=1.0-SNAPSHOT -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.1 org.apache.maven.plugins:maven-archetype-plugin:RELEASE:generate [INFO] Scanning for projects... Downloading: https://cmc.centralrepo.rnd.huawei.com/maven/org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml Downloading: https://dgg.maven.repo.cmc.tools.huawei.com/artifactory/BPIT-public-maven/org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml [WARNING] Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to artifact-plugins (https://dgg.maven.repo.cmc.tools.huawei.com/artifactory/BPIT-public-maven/): PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to dg-artifact (https://cmc.centralrepo.rnd.huawei.com/maven/): PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.377 s [INFO] Finished at: 2025-06-10T20:52:53+08:00 [INFO] Final Memory: 9M/48M [INFO] ------------------------------------------------------------------------ [ERROR] Plugin org.apache.maven.plugins:maven-archetype-plugin:RELEASE or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-archetype-plugin:jar:RELEASE: Failed to resolve version for org.apache.maven.plugins:maven-archetype-plugin:jar:RELEASE: Could not find metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml in local (C:\04_DevTools\maven_repo2) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
06-11
PluginResolutionException: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.5 from/to nexus-aliyun ``` 这可能是由于以下原因之一导致的： - **仓库地址错误或不可达** 确保`...
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@584f5497 [DEBUG] (s) silent = false [DEBUG] (s) skip = false [DEBUG] (s) useJvmChmod = true [DEBUG] -- end configuration -- [INFO] Configured Artifact: com.alibaba.lindorm.sqlminds:ldml-exec:osx-aarch_64:1.3.4.2:jar [DEBUG] Using transporter WagonTransporter with priority -1.0 for http://mvnrepo.alibaba-inc.com/mvn/repository [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://mvnrepo.alibaba-inc.com/mvn/repository Downloading from alibaba-releases: http://mvnrepo.alibaba-inc.com/mvn/repository/com/alibaba/lindorm/sqlminds/ldml-exec/1.3.4.2/ldml-exec-1.3.4.2-osx-aarch_64.jar [DEBUG] Writing tracking file /Users/lvzhuoyuan/.m2/repository/com/alibaba/lindorm/sqlminds/ldml-exec/1.3.4.2/ldml-exec-1.3.4.2-osx-aarch_64.jar.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://maven.aliyun.com/repository/public [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://maven.aliyun.com/repository/public Downloading from aliyun: https://maven.aliyun.com/repository/public/com/alibaba/lindorm/sqlminds/ldml-exec/1.3.4.2/ldml-exec-1.3.4.2-osx-aarch_64.jar [DEBUG] Writing tracking file /Users/lvzhuoyuan/.m2/repository/com/alibaba/lindorm/sqlminds/ldml-exec/1.3.4.2/ldml-exec-1.3.4.2-osx-aarch_64.jar.lastUpdated [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for Lindorm ML Project 1.3.4.2: [INFO] [INFO] Lindorm ML Project ................................. SUCCESS [ 0.180 s] [INFO] ldml-sql ........................................... SUCCESS [ 1.929 s] [INFO] ldml-inference-client .............................. SUCCESS [ 7.685 s] [INFO] ldml-core .......................................... SUCCESS [ 6.969 s] [INFO] ldml-jdbc .......................................... SUCCESS [ 0.563 s] [INFO] ldml-train ......................................... SUCCESS [ 0.778 s] [INFO] ldml-inference ..................................... SUCCESS [ 1.571 s] [INFO] ldml-exec .......................................... SUCCESS [ 7.251 s] [INFO] ldml-server ........................................ SUCCESS [ 0.880 s] [INFO] ldml-endpoint-lsql ................................. FAILURE [ 1.662 s] [INFO] dist-ldml-server ................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 30.130 s [INFO] Finished at: 2025-06-24T12:00:59+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.3.0:unpack (unpack-ldml-template) on project ldml-endpoint-lsql: Unable to find/resolve artifact.: Could not find artifact com.alibaba.lindorm.sqlminds:ldml-exec:jar:osx-aarch_64:1.3.4.2 in alibaba-releases (http://mvnrepo.alibaba-inc.com/mvn/repository), try downloading from http://gitlab.alibaba-inc.com/lindorm_ml/lindorm-ml/ -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.3.0:unpack (unpack-ldml-template) on project ldml-endpoint-lsql: Unable to find/resolve artifact. at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to find/resolve artifact. at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact (AbstractFromConfigurationMojo.java:256) at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems (AbstractFromConfigurationMojo.java:172) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.getProcessedArtifactItems (UnpackMojo.java:161) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.doExecute (UnpackMojo.java:111) at org.apache.maven.plugins.dependency.AbstractDependencyMojo.execute (AbstractDependencyMojo.java:150) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.apache.maven.shared.transfer.artifact.resolve.ArtifactResolverException: Could not find artifact com.alibaba.lindorm.sqlminds:ldml-exec:jar:osx-aarch_64:1.3.4.2 in alibaba-releases (http://mvnrepo.alibaba-inc.com/mvn/repository), try downloading from http://gitlab.alibaba-inc.com/lindorm_ml/lindorm-ml/ at org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact (Maven31ArtifactResolver.java:101) at org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact (Maven31ArtifactResolver.java:78) at org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:70) at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact (AbstractFromConfigurationMojo.java:252) at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems (AbstractFromConfigurationMojo.java:172) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.getProcessedArtifactItems (UnpackMojo.java:161) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.doExecute (UnpackMojo.java:111) at org.apache.maven.plugins.dependency.AbstractDependencyMojo.execute (AbstractDependencyMojo.java:150) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact com.alibaba.lindorm.sqlminds:ldml-exec:jar:osx-aarch_64:1.3.4.2 in alibaba-releases (http://mvnrepo.alibaba-inc.com/mvn/repository), try downloading from http://gitlab.alibaba-inc.com/lindorm_ml/lindorm-ml/ at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:424) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:207) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact (DefaultRepositorySystem.java:262) at org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact (Maven31ArtifactResolver.java:97) at org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact (Maven31ArtifactResolver.java:78) at org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:70) at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact (AbstractFromConfigurationMojo.java:252) at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems (AbstractFromConfigurationMojo.java:172) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.getProcessedArtifactItems (UnpackMojo.java:161) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.doExecute (UnpackMojo.java:111) at org.apache.maven.plugins.dependency.AbstractDependencyMojo.execute (AbstractDependencyMojo.java:150) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact com.alibaba.lindorm.sqlminds:ldml-exec:jar:osx-aarch_64:1.3.4.2 in alibaba-releases (http://mvnrepo.alibaba-inc.com/mvn/repository), try downloading from http://gitlab.alibaba-inc.com/lindorm_ml/lindorm-ml/ at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed (ArtifactTransportListener.java:48) at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run (BasicRepositoryConnector.java:369) at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run (RunnableErrorForwarder.java:75) at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute (BasicRepositoryConnector.java:644) at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get (BasicRepositoryConnector.java:262) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads (DefaultArtifactResolver.java:499) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:401) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:207) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact (DefaultRepositorySystem.java:262) at org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact (Maven31ArtifactResolver.java:97) at org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact (Maven31ArtifactResolver.java:78) at org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:70) at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getArtifact (AbstractFromConfigurationMojo.java:252) at org.apache.maven.plugins.dependency.fromConfiguration.AbstractFromConfigurationMojo.getProcessedArtifactItems (AbstractFromConfigurationMojo.java:172) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.getProcessedArtifactItems (UnpackMojo.java:161) at org.apache.maven.plugins.dependency.fromConfiguration.UnpackMojo.doExecute (UnpackMojo.java:111) at org.apache.maven.plugins.dependency.AbstractDependencyMojo.execute (AbstractDependencyMojo.java:150) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :ldml-endpoint-lsql lvzhuoyuan@U-VF56K71F-1930 lindormML % 帮我看看
06-25
步骤2：检查仓库配置在pom.xml或settings.xml中配置的alibaba-releases仓库的URL是什么？常见的阿里巴巴仓库是https://reposity.alibaba.com/repository/public/，但具体到某个团队可能不同。确认URL是否正确。步骤3...
eclipse配置Maven Settings.xml文件报错：Could not read settings.xml
weixin_40601536的博客
05-06 8583
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
ifnotcorrect的博客
07-24 227
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
huawangxin
06-13 2529
maven碰到了配置错误 错误信息: 解决方法: 可以看到再次点击Browse选择settings.xml文件后出现了警告：Unable to parse global ...\u7a9d\n<m... @226:3) , 这个226说明第226行出现了错误，导致了文件不能正常读取，仔细检查该行有没有错误或者中文信息。 更改后： 这个错误是settings.xml内标签配置有问题，替换正确的标签信息后能够解决。 放一下使用的路径配置：<localRepository&g...
解决maven提示：Could not read settings.xml, assuming default values 错误
蓝缘
10-13 2万+
原因可能有两个： 1.settings.xml的格式有问题，（可以拿别来对照下） 2.有可能是repository仓库有问题。（路径最好不要有中文）
maven配置setting.xml报Could not read settings.xml
zhou920786312的博客
08-02 1万+
Could not read settings.xml, assuming default values解决 1settings.xml不能有中文 2settings.xml 路径的标识是/
eclipse maven - could not read settings.xml
深度
10-31 307
我也不知道为啥突然好了 但我貌似改了这些配置 1. settings.xml <mirrors> <mirror> <id>nexus-aliyun</id> <mirrorOf>central</mirrorOf> <name>Nexus aliyun</name> ...
mvn 学习总结.不断更新中....
杨锋的blog
01-09 1040
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配置usersetting时出现Could not read settings.xml
说好的
10-26 1114
我add完maven然后再设置好xml路径，一顿配置完了之后就没管它，直到新建一个maven项目，添加parent依赖的时候出报错，才排查到这里。 步骤： 再点一次Browse重新选择此xml文件路径，然后上面就会报xml出错的行数，去看有没有重复标签、中文字符、注释内容，有的话全部删掉，重复标签合并一下。就解决了！ ...
在 eclipse， Could not read setting.xml
HCS11的博客
10-14 492
在 eclipse， Could not read setting.xml
评论 3
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

悟世君子

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值