2020年：maven配置最新阿里雲映象，以及在IDEA中的設定

只有光頭才能強發表於2020-12-01

Maven阿里Idea

記得當初學習Maven的時候，由國外的中央倉庫切換為阿里雲映象之後，用起來是辣麼地絲滑~

不過最近一段時間，Maven卻總是出現一些問題，本地庫裡總是出現一些.lastUpdated檔案，類似於下面這種。

在這裡插入圖片描述

一開始以為是網路的原因，並沒有很重視。直至昨晚，pom再次飄紅，研究了一下，才發現問題的根源所在。

通過查閱資料得知：阿里雲的Maven映象已經做了https升級和倉庫細化，以前的配置方式已失效！

在這裡插入圖片描述

原來的映象配置：

<mirror>
    <id>nexus-aliyun</id>
    <mirrorOf>central</mirrorOf>
    <name>Nexus aliyun</name>
    <url>http://maven.aliyun.com/nexus/content/groups/public</url>
</mirror>

更新後的配置為：

<mirror>
    <id>aliyunmaven</id>
    <mirrorOf>*</mirrorOf>
    <name>阿里雲公共倉庫</name>
    <url>https://maven.aliyun.com/repository/public</url>
</mirror>

在這裡插入圖片描述

此外，由於使用了https，存在著SSL證書驗證的問題。所以，在修改完maven的settings檔案之後，還需要在IDEA的File->Setting中進行設定，忽略SSL證書的驗證。（ps：上午試著新增阿里maven倉庫https證書，搞了半天也不好使，最終選擇了忽略。新增倆小時，忽略兩分鐘。簡單粗暴！哈哈…）

在這裡插入圖片描述

1. 解決依賴無法下載

IDEA中更改設定：

在這裡插入圖片描述

-Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true

2. 解決maven無法compile

在這裡插入圖片描述

-Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true

至此，理論上來講，maven就又可以絲滑地使用了。

如果還是不行，可以參考這一篇部落格，他的方法二提供了另外一種思路：Idea通過Maven構建springboot專案時失敗

另附一個maven的settings檔案配置資訊，供交流學習討論。（基於apache-maven-3.5.4版本的）

<?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>D:\Program Files\RepMaven</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>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</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>
     -->
	<!-- 阿里雲Maven映象倉庫 該倉庫目前存在於北京市大興區 -->
	<!-- 
	<mirror>
		<id>alimaven</id>
		<name>aliyun maven</name>
		<url>http://maven.aliyun.com/nexus/content/groups/public/</url>
		<mirrorOf>central</mirrorOf>
    </mirror>
	 -->
	<mirror>
		<id>aliyunmaven</id>
		<mirrorOf>*</mirrorOf>
		<name>Nexus aliyun</name>
		<url>https://maven.aliyun.com/repository/public</url>
	</mirror>
	<!-- CN國內Maven映象倉庫 該倉庫目前存在於浙江省杭州市 -->
	<mirror>
		<id>net-cn</id>
		<mirrorOf>central</mirrorOf>
		<name>Human Readable Name for this Mirror.</name>
		<url>http://maven.net.cn/content/groups/public/</url>
    </mirror>
	<!-- 網易163Maven映象倉庫 該倉庫目前存在於廣東省廣州市 -->
	<mirror>
		<id>nexus-163</id>
		<mirrorOf>*</mirrorOf>
		<name>Nexus 163</name>
		<url>http://mirrors.163.com/maven/repository/maven-public/</url>
	</mirror>
	<!-- ibiblio地址是美國的，但用起來感覺還是比較快的，而且還不用X牆的，非常nice -->
	<mirror>
	    <id>ibiblio</id>
	    <name>Mirror from Maven ibiblio</name>
	    <url>http://mirrors.ibiblio.org/pub/mirrors/maven2/</url>
	    <mirrorOf>central</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>jdk-1.8</id>
		<activation>
			<activeByDefault>true</activeByDefault>	
			<jdk>1.8</jdk>
		</activation>
		<properties>
			<maven.compiler.source>1.8</maven.compiler.source>
			<maven.compiler.target>1.8</maven.compiler.target>
			<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
		</properties>
		<!-- dubbo 官方的解決方案 -->
		<repositories>
			<repository>
				<id>sonatype-nexus-snapshots</id>
				<url>https://oss.sonatype.org/content/repositories/snapshots</url>
				<releases>
					<enabled>false</enabled>
				</releases>
				<snapshots>
					<enabled>true</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
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

Maven配置阿里雲映象
2021-02-25
Maven阿里
idea中設定maven預設位置
2020-10-30
IdeaMaven
IDEA中Maven的配置
2021-04-23
IdeaMaven
在Intellij IDEA中如何配置Maven
2018-10-28
IntelliJIdeaMaven
Maven國內映象地址配置（整理了最新可用的源）
2024-03-22
Maven
Docker配置阿里雲映象加速器以及映象的常用操作命令
2020-10-29
Docker阿里
idea配置maven
2024-04-06
IdeaMaven
maven 多倉庫和映象設定
2019-01-19
Maven
2020年最新可用的谷歌映象站
2020-09-25
谷歌
[idea中配置maven]
2017-09-03
IdeaMaven
在eclipse中maven配置
2020-10-31
EclipseMaven
idea maven怎麼安裝配置 idea maven配置教程詳細圖解
2022-05-04
IdeaMaven圖解
安裝maven，並將其配置到idea中
2018-05-29
MavenIdea
在idea上 maven 打包
2020-11-13
IdeaMaven
新版idea配置maven注意點！！
2024-03-13
IdeaMaven
最新 IDEA 和 Maven 整合問題和解決
2019-02-20
IdeaMaven
【Java】【專案構建】Idea中設定Gradle/Maven多模組依賴
2019-06-30
JavaIdeaGradleMaven
npm配置淘寶映象倉庫以及electron映象
2020-07-10
NPM
配置阿里雲RepoForge 映象
2022-03-10
阿里
maven設定阿里雲映象源，jdk8，本地倉庫路徑節省C盤空間
2020-12-28
Maven阿里JDK
在idea中利用spingboot建立maven專案
2020-12-29
IdeabootMaven
Intellij IDEA-IDEA中配置Maven Tomcat
2017-05-12
IntelliJIdeaMavenTomcat
最新版idea不區分大小寫設定
2018-08-20
Idea
Eclipse阿里雲映象源配置
2022-02-10
Eclipse阿里
IDEA中Usage提示功能設定
2023-02-20
Idea
你還再為下載jar包慢而煩惱嗎？Maven配置阿里雲映象
2020-11-11
JARMaven阿里
解決IDEA中maven中的module是灰色的
2020-12-24
IdeaMaven
scalatest在idea和maven中執行錯誤的問題解決
2014-11-07
IdeaMaven
Redis 哨兵使用以及在 Laravel 中的配置
2019-06-28
RedisLaravel
maven 在pom檔案下配置預設的jdk版本
2017-06-12
MavenJDK
Grafana映象在阿里雲映象站首發上線
2022-01-19
Grafana阿里
ClickHouse映象在阿里雲映象站首發上線
2022-03-14
阿里
Termux映象在阿里雲映象站首發上線
2022-03-17
UX阿里
Maven配置中遇到的坑
2017-06-02
Maven
Mac 中 Maven 配置
2020-07-01
MacMaven
windows下使用idea maven配置spark執行環境、執行WordCount例子以及碰到的問題
2017-12-28
WindowsIdeaMavenSpark
maven配置阿里雲及本地倉庫
2020-12-02
Maven阿里
Docker配置阿里雲映象加速器
2020-11-06
Docker阿里

2020年：maven配置最新阿里雲映象，以及在IDEA中的設定

相關文章