Jue suis entrain de faire une application en utilisant spring boot，maven（v 3.3.9）司法鉴定书：
错误
[警告] [警告]构建有效设置时遇到了一些问题 [警告]无法识别的标记：“存储库”（位置：已看到START_TAG ... \ n \ n ... @ 74：16）@ C：\ Users \ 04977.m2 \ settings.xml，第74行，第16列 [警告] [INFO]正在扫描项目... [INFO]下载：https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/1.5.9.RELEASE/spring-boot-starter-parent-1.5.9.RELEASE.pom [错误] [错误]处理POM时遇到了一些问题：
[FATAL] org.sid：MyCatalogue：0.0.1-SNAPSHOT的不可解析的父POM：无法传输工件org.springframework.boot：spring-boot-starter-parent：pom：1.5.9从/到中央（https://repo.maven.apache.org/maven2的.RELEASE：sun.security.validator.ValidatorException：PKIX路径构建失败：sun.security.provider.certpath.SunCertPathBuilderException：无法找到到请求的目标和“父”的有效证书路径。 relativePath'指向第14行第10列处没有本地POM @
[错误]构建无法读取1个项目-> [帮助1]
[错误]
[错误]项目org.sid：MyCatalogue：0.0.1-SNAPSHOT（C：\ WorkspaceSpringAngular \ MyCatalogue \ pom.xml）有1个错误
[错误] org.sid：MyCatalogue：0.0.1-SNAPSHOT的不可解析的父POM：无法将工件org.springframework.boot：spring-boot-starter-parent：pom：1.5.9.RELEASE从中央转移到中央（https://repo.maven.apache.org/maven2）：sun.security.validator.ValidatorException：PKIX路径构建失败：sun.security.provider.certpath.SunCertPathBuilderException：无法找到到请求的目标的有效证书路径和没有本地的“ parent.relativePath”点POM @第14行，第10列-> [帮助2]
[错误]
[错误]要查看错误的完整堆栈跟踪，请使用-e开关重新运行Maven。
[错误]使用-X开关重新运行Maven以启用完整的调试日志记录。
[错误]
[ERROR]有关错误和可能的解决方案的详细信息，请阅读以下文章：
[错误] [帮助1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[错误] [帮助2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
FIN错误
https://repo.maven.apache.org/maven2的dépendancesméàjévoudrais avoir votre aide倒了。 Voilàmon settings.xml：
<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>/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: 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 for HTTP -->
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>username</username>
<password>password</password>
<host>host</host>
<port>port</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> -->
</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> -->
</profiles>
<!-- activeProfiles | List of profiles that are active for all builds. |
<activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile>
</activeProfiles> -->
</settings>
首先确认monProjet / .mvc：未安装jvm.config内容：
-Dhttp.proxyHost=host
-Dhttp.proxyPort=port
-Dhttp.proxyUser=username
-Dhttp.proxyPassword=password
-Dmaven.wagon.http.ssl.insecure=true
-Dmaven.wagon.http.ssl.allowall=true
-Dmaven.wagon.http.ssl.ignore.validity.dates=true
答案 0 :(得分：0)
我建议删除.mvc文件夹并修复settings.xml。
WARNING] Unrecognised tag: 'repository' (position: START_TAG seen ...\n\n ... @74:16)
如果您位于代理之后，只需要做的就是正确配置settings.xml