java - Maven 没有在代理环境中引用本地仓库
问题描述
背景：我们处于基于代理的环境中。我们的安全团队将 Maven Central 列入白名单需要时间。因此，我们手动将项目的依赖项下载到 Jenkins 代理的~.m2/repository文件夹中，以开始构建自动化之旅。
Nexus是我们的工件发布平台。
问题是 Maven 不是指存储在 m2 文件夹中的依赖项。它总是试图连接互联网以下载 deps。
这是我们的 pom.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.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>/path/to/local/repo</localRepository>
-->
<localRepository>C:\Users\Netadmin\.m2\repository</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>
<id>nexus-abcd</id>
<active>true</active>
<protocol>http</protocol>
<username>abcd</username>
<password>abcd@1213</password>
<host>proxylb.abcd.com</host>
<port>80</port>
</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>
-->
<server>
<id>sdg-snapshots</id>
<username>admin</username>
<password>admin@123</password>
</server>
<server>
<id>sdg-releases</id>
<username>admin</username>
<password>admin@123</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>sdg-group</id>
<name>sdg-group</name>
<url>http://xx.xx.xx.xxx:9043/repository/sdg-group/</url>
<mirrorOf>*</mirrorOf>
</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>
-->
<profile>
<id>sdg</id>
<repositories>
<repository>
<id>releases</id>
<name>SDGReleaseRepository</name>
<url>http://xx.xx.xx.xxx:9043/repository/sdg-releases/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</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>
<activeProfile>sdg</activeProfile>
</activeProfiles>
</settings>
我们还注释掉了关系设置，但面临相同的构建时间错误（无法下载依赖项）。
如何让 Maven 引用本地存储库？
错误日志：
12:02:33 C:\Users\Netadmin\.jenkins\workspace\MART\MART_Project>D:\apache-maven-3.6.1-bin\apache-maven-3.6.1\bin\mvn -o -f parent/pom.xml clean compile install -e
12:02:35 [INFO] Error stacktraces are turned on.
12:02:35 [INFO] Scanning for projects...
12:02:35 [WARNING]
12:02:35 [WARNING] Some problems were encountered while building the effective model for com.icici:cmart-schedular:jar:1.0
12:02:35 [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.commons:commons-csv:jar -> duplicate declaration of version 1.0 @ line 120, column 15
12:02:35 [WARNING]
12:02:35 [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
12:02:35 [WARNING]
12:02:35 [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
12:02:35 [WARNING]
12:02:35 [INFO] ------------------------------------------------------------------------
12:02:35 [INFO] Reactor Build Order:
12:02:35 [INFO]
12:02:35 [INFO] parent [pom]
12:02:35 [INFO] mart-framework [jar]
12:02:35 [INFO] mart-domain [jar]
12:02:35 [INFO] mart-transfer-object [jar]
12:02:35 [INFO] mart-fi-integration [jar]
12:02:35 [INFO] mart-web [war]
12:02:35 [INFO] mart-report [war]
12:02:35 [INFO] mart-schedular [jar]
12:02:35 [INFO] mart-web-scheduler [war]
12:02:35 [INFO]
12:02:35 [INFO] --------------------------< com.icici:parent >--------------------------
12:02:35 [INFO] Building parent 1.0 [1/9]
12:02:35 [INFO] --------------------------------[ pom ]---------------------------------
12:02:35 [INFO]
12:02:35 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ parent ---
12:02:35 [INFO] ------------------------------------------------------------------------
12:02:35 [INFO] Reactor Summary:
12:02:35 [INFO]
12:02:35 [INFO] parent 1.0 ......................................... FAILURE [ 0.147 s]
12:02:35 [INFO] mart-framework 1.0 ................................ SKIPPED
12:02:35 [INFO] mart-domain 1.0 ................................... SKIPPED
12:02:35 [INFO] mart-transfer-object 1.1 .......................... SKIPPED
12:02:35 [INFO] mart-fi-integration 1.0 ........................... SKIPPED
12:02:35 [INFO] mart-web 1.0 ...................................... SKIPPED
12:02:35 [INFO] mart-report 1.0 ................................... SKIPPED
12:02:35 [INFO] mart-schedular 1.0 ................................ SKIPPED
12:02:35 [INFO] mart-web-scheduler 1.0 ............................ SKIPPED
12:02:35 [INFO] ------------------------------------------------------------------------
12:02:35 [INFO] BUILD FAILURE
12:02:35 [INFO] ------------------------------------------------------------------------
12:02:35 [INFO] Total time: 0.399 s
12:02:35 [INFO] Finished at: 2019-07-31T12:02:35+05:30
12:02:35 [INFO] ------------------------------------------------------------------------
12:02:35 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project parent: Execution default-clean of goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean failed: Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven:maven-plugin-api:jar:2.0.6 has not been downloaded from it before. -> [Help 1]
12:02:35 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project parent: Execution default-clean of goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean failed: Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven:maven-plugin-api:jar:2.0.6 has not been downloaded from it before.
POM 文件：
<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.abcd</groupId>
<artifactId>parent</artifactId>
<version>1.0</version>
<packaging>pom</packaging>
<scm>
<url>scm:svn:https://abcd/svn/mart-workspace/branches/mart-maven</url>
<connection>scm:svn:https://abcd/svn/repos/mart_code_workspace/branches/mart-maven</connection>
<developerConnection>scm:svn:https://abcd/svn/repos/mart_code_workspace/branches/mart-maven</developerConnection>
<tag>HEAD</tag>
</scm>
<modules>
<module>../mart-domain</module>
<module>../mart-framework</module>
<module>../mart-transfer-object</module>
<module>../mart-fi-integration</module>
<module>../mart-web</module>
<module>../mart-report</module>
<module>../mart-schedular</module>
<module>../mart-web-scheduler</module>
</modules>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.2</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.9.2</version>
<configuration>
<connectionType>connection</connectionType>
<goals>install</goals>
</configuration>
</plugin>
</plugins>
</build>
<!-- <distributionManagement>
<snapshotRepository>
<id>sdg-snapshots</id>
<url>http://xx.xx.xx.xxx:9043/repository/sdg-snapshots/</url>
</snapshotRepository>
<repository>
<id>sdg-releases</id>
<url>http://xx.xx.xx.xxx:9043/repository/sdg-releases/</url>
</repository>
</distributionManagement>
-->
</project>
注意 1：构建在 Eclipse 中成功进行（引用了本地存储库）。我们将桌面的 m2 repo 文件夹粘贴到服务器的 m2 文件夹中。理想情况下，詹金斯中的 Maven 应该可以工作。
注意 2：我们已经在这个新更新中注释掉了 Pom 和 settings.xml 文件中的 Nexus 设置。它的行为仍然与 maven 尝试联系 maven 中央回购的方式相同。
问候
解决方案
从Maven CLI 选项中，您可以简单地强制它以离线模式运行：
mvn -o install或者mvn --offline install
为什么它看起来很遥远？正如@KrisT 所指出的那样，您可能在本地缺少一些依赖项。
或者您可以使用 -SNAPSHOT。
-U,--update-snapshots强制检查远程存储库上的更新版本和快照。这通常由updatePolicy管理：
updatePolicy：此元素指定尝试更新的频率。Maven 会将本地 POM 的时间戳（存储在存储库的 maven-metadata 文件中）与远程进行比较。选择是：总是、每天（默认）、间隔：X（其中 X 是以分钟为单位的整数）或从不。
本质上，如果使用 SNAPSHOTS，它每天都会远程查找新的 SNAPSHOT 或版本。
假设您在本地拥有所有依赖项，请使用该--offline选项。请记住，您实际上正在使用该选项，因为它是不正常的，如果您缺少更新的依赖项，甚至是内部的依赖项，您将追赶幽灵，特别是如果每个开发人员负责保持自己的本地更新！
另外两个想法：
- 考虑设置一个单独的帐户，而不是具有部署工件权限的“管理员”而不是“管理员”权限，Jenkins 的服务帐户或在 Nexus 中设置单个用户；更好的可追溯性和更安全。事实上，创建一个单独的命名用户为 admin 并一起禁用 admin 帐户！
- Eclipse 通过其插件之一使用不同的机制，众所周知，让 Eclipse 本地构建和运行之间的行为差异
mvn install是不同的。
ps：相反的问题可以麻烦其他人。一天内多次远程更新的 SNAPSHOT 不会在本地再次拉下，除非强制-U,--update-snapshot或调用maven-dependency-plugin
dependency:purge-local-repository告诉 Maven 从本地存储库中清除依赖项工件文件，并可选择重新解析它们。
从而强制远程获取。
您的 build.log 显示了一个问题，但可能无关：
12:02:35 [WARNING] Some problems were encountered while building the effective model for com.icici:cmart-schedular:jar:1.0
12:02:35 [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.commons:commons-csv:jar -> duplicate declaration of version 1.0 @ line 120, column 15
调查选项
在您的帖子更新之后，这表明您实际上仍然在本地缺少一些依赖项，无论是直接的、传递的还是插件的，都在外部强制搜索。我会提出一些想法，但我不确定如果您无法更新本地存储库（您第一次是如何在那里获得罐子的？），您将如何解决它们。
Maven 帮助提供了一些配置见解：
mvn help:effective-settings: 目标用于查看 Maven 实际用于运行构建的设置。这些设置是将全局文件与用户文件合并的结果，其中用户文件优先。
mvn help:effective-pom: 目标用于使由应用插值、继承和活动配置文件产生的 POM 可见。它提供了一种有用的方法来消除关于 Maven 用于构建项目的 POM 中最终结果的猜测。
Maven Dependency 插件提供了一些应用依赖洞察：
mvn dependency:go-offline：解决所有项目依赖项的目标，包括插件和报告及其依赖项。
mvn dependency:list并mvn dependency:resolve-plugins提供有关依赖项或插件的特定信息
当然，问题可能是为了执行这些，您必须在本地拥有插件及其依赖项。为了有效地处理列表，您还必须具有依赖项。
您可以执行 afind ~/.m2/repository -name "*.jar" -a ! -name "*.sources.jar" -a ! -name "*.javadoc.jar"以获取本地所有 jar 的列表
推荐阅读
- php - 是什么导致了这个“Missing argument 2 for Categories::posts()”错误？
- python - 如何对unittest测试用例进行排序？
- python - 如何在数据集中添加异常
- visual-studio-code - 如何在 VS Code 侧边栏中预览打开的端口？
- docker - 连接 dockerized 应用程序网络以进行 api 调用
- json - 如何抓取包含在 HTML 页面中的 JSON 标记
- javascript - How to update the table when same record is inserted using jquery
- list - 返回列表中的特定元素 - LISP
- swift - 如何在@propertyWrapper 中获取父母的自我？
- android - Installation did not succeed. The application could not be installed. Installation failed due to: