MacOS安装Java+mvn+mvnd+jenv多环境丝滑切换

一、初衷

  1. java sdk 版本升级较快, 个人在多项目开发过程当中, 客户对接过程当中, jdk的版本不一致, 时常来回手动切换各个插件间(Java、mvn、mvnd)的版本(烦躁)
  2. 学习一下mvnd, 据说mvnc的效率要比mvn高很多
  3. 利用jenv无感各个组件之间的JDK版本切换

二、资源整理

  1. 以下所有安装环境都是在MacOS操作系统下进行
  2. Maven下载地址: https://dlcdn.apache.org/maven/maven-3/3.9.12/binaries/apache-maven-3.9.12-bin.zip
  3. Maven Daemon下载地址: https://dlcdn.apache.org/maven/mvnd/1.0.3/maven-mvnd-1.0.3-darwin-amd64.zip
  4. jenv、java sdk 通过brew安装
  5. 在~/下创建software/maven文件夹, 存放安装包、第三方下载包等, 个人习惯将开发相关的插件、软件存放此处, 如下
css 复制代码
╭─░▒▓  │  ~/software  ❯ ls
ai             chrome         cursor         easyconnect    graalvm-images jetbrain       kustomize      nexus          typora         xpipe
axure8         cleanmymac     deepseek       github         helm           ktconnect      maven          nodejs         vmware
centos         comfyui        docker         go             iterm2         kubectl        navicat        rust           xcode

╭─░▒▓  │  ~/software  ❯ 

三、环境安装

  1. Java SDK安装
    • 安装官方 Tap 版, 5个版本, 没办法, 项目比较杂乱😭
    • 我这里选择graalvm, 后考虑玩玩graalvm
css 复制代码
╭─░▒▓  │  ~/software  ❯ brew tap graalvm/tap

╭─░▒▓  │  ~/software  ❯ brew install graalvm/tap/graalvm-ce-lts-java8
╭─░▒▓  │  ~/software  ❯ brew install graalvm/tap/graalvm-ce-lts-java11
╭─░▒▓  │  ~/software  ❯ brew install graalvm/tap/graalvm-jdk17
╭─░▒▓  │  ~/software  ❯ brew install graalvm/tap/graalvm-jdk21
╭─░▒▓  │  ~/software  ❯ brew install graalvm/tap/graalvm-jdk25

## 配置JDK
╭─░▒▓  │  ~/software  ❯ vi ~/.zshrc
export JAVA_08_HOME=/Library/Java/JavaVirtualMachines/graalvm-ce-lts-java8-20.3.1/Contents/Home
export JAVA_11_HOME=/Library/Java/JavaVirtualMachines/graalvm-ce-lts-java11-20.3.4/Contents/Home
export JAVA_17_HOME=/Library/Java/JavaVirtualMachines/graalvm-jdk-17/Contents/Home
export JAVA_21_HOME=/Library/Java/JavaVirtualMachines/graalvm-jdk-21/Contents/Home
export JAVA_25_HOME=/Library/Java/JavaVirtualMachines/graalvm-jdk-25/Contents/Home

╭─░▒▓  │  ~/software  ❯ source ~/.zshrc
  1. 安装并配置jenv
css 复制代码
## 安装jenv, 编辑~/.zshrc添加环境变量

╭─░▒▓  │  ~/software  ❯ brew install jenv
jenv 0.6.0

╭─░▒▓  │  ~/software  ❯ vi ~/.zshrc
export PATH="$HOME/.jenv/bin:$PATH"
eval "$(jenv init -)"

╭─░▒▓  │  ~/software  ❯ source ~/.zshrc
  • 添加JDK到jenv
  • 注意, JDK8、JDK11,提示文件已经损坏, 如下配置
css 复制代码
## 这里提示已经损坏, 实则是权限问题, 在隐私与安全性位置放开即可, 我习惯执行命令, 如下

xattr -r -d com.apple.quarantine /Library/Java/JavaVirtualMachines/graalvm-ce-lts-java8-20.3.1/
xattr -r -d com.apple.quarantine /Library/Java/JavaVirtualMachines/graalvm-ce-lts-java11-20.3.4/

## 如果添加不上, 手动添加
## 进入 ~/.jenv/versions

ln -s $JAVA_08_HOME 8
ln -s $JAVA_11_HOME 11

╭─░▒▓  │  ~/software  ❯ jenv add $JAVA_08_HOME                                                                                                                                            
╭─░▒▓  │  ~/software  ❯ jenv add $JAVA_11_HOME
╭─░▒▓  │  ~/software  ❯ jenv add $JAVA_17_HOME
╭─░▒▓  │  ~/software  ❯ jenv add $JAVA_21_HOME
╭─░▒▓  │  ~/software  ❯ jenv add $JAVA_25_HOME
  • 查看jenv列表
  • 这里有很多杂乱的版本, 其实相同大版本后面的小版本号指向是同一个版本, 可以删除
css 复制代码
╭─░▒▓  │  ~/software  ❯ jenv versions
jenv: version `21' is not installed
  system
  11
  17.0
  17.0.12
  21.0
  21.0.9
  25
  25.0
  25.0.1
  8
  graalvm64-17.0.12
  graalvm64-21.0.9
  graalvm64-25.0.1

## 删除命令(可选)
╭─░▒▓  │  ~/software  ❯ jenv remove 17.0

## 整理后如下(可选, 个人习惯留一个大版本, 留一个精确版本)
╭─░▒▓  │  ~/software  ❯ jenv versions
jenv: version `21' is not installed
  system
  8
  11
  17
  17.0.12
  21
  21.0.9
  25
  25.0.1

## 版本切换
╭─░▒▓  │  ~/software  ❯ jenv local 21

# 重建 jenv 缓存
╭─░▒▓  │  ~/software  ❯ jenv rehash
  1. 手动安装Maven(个人习惯手动安装, 好维护和管理)

    • 目录如下, 两个zip包(安装后可删除)

    • repository是执行mvn install等命令安装的第三方包存放的地方

css 复制代码
╭─░▒▓  │  ~/software  ❯  cd maven
╭─░▒▓  │  ~/software  ❯  ll
total 65728
drwxr-xr-x@  9 xincan  staff   288B 12月 13 09:16 apache-maven-3.9.12
-rw-r--r--@  1 xincan  staff   8.9M 12月 24 09:01 apache-maven-3.9.12-bin.zip
drwxrwxr-x@  8 xincan  staff   256B  1月  1  1980 maven-mvnd-1.0.3-darwin-amd64
-rw-r--r--@  1 xincan  staff    22M 12月 24 09:00 maven-mvnd-1.0.3-darwin-amd64.zip
drwxr-xr-x  59 xincan  staff   1.8K  2月 10  2025 repository
  • 配置maven、mvnd
css 复制代码
╭─░▒▓  │  ~/software  ❯ vi ~/.zshrc
# config set maven version
export MAVEN_HOME=/Users/xincan/software/maven/apache-maven-3.9.12
export PATH=$PATH:$MAVEN_HOME/bin

# config set mvnd version
export MVND_HOME=/Users/xincan/software/maven/maven-mvnd-1.0.3-darwin-amd64
export PATH=$PATH:$MVND_HOME/bin

╭─░▒▓  │  ~/software  ❯ source ~/.zshrc
  • 建议重启终端

四、版本验证

css 复制代码
╭─░▒▓  │  ~/software  ❯ jenv versions
  system
  11
  17.0.12
* 21 (set by /Users/xincan/.jenv/versions/.java-version)
  21.0.9
  25
  25.0.1
  8
  
╭─░▒▓  │  ~/software  ❯ java -version
java version "21.0.9" 2025-10-21 LTS
Java(TM) SE Runtime Environment Oracle GraalVM 21.0.9+7.1 (build 21.0.9+7-LTS-jvmci-23.1-b79)
Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 21.0.9+7.1 (build 21.0.9+7-LTS-jvmci-23.1-b79, mixed mode, sharing)

╭─░▒▓  │  ~/software  ❯ mvn -v
Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1)
Maven home: /Users/xincan/software/maven/apache-maven-3.9.12
Java version: 21.0.9, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/graalvm-jdk-21/Contents/Home
Default locale: zh_CN_#Hans, platform encoding: UTF-8
OS name: "mac os x", version: "26.2", arch: "x86_64", family: "mac"

╭─░▒▓  │  ~/software  ❯ mvnd -v
Apache Maven Daemon (mvnd) 1.0.3 darwin-amd64 native client (824a1fd42088e27dec6cc7cc392b9122379e7bf0)
Terminal: org.jline.terminal.impl.PosixSysTerminal with pty org.jline.terminal.impl.jni.osx.OsXNativePty
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /Users/xincan/software/maven/maven-mvnd-1.0.3-darwin-amd64/mvn
Java version: 21.0.9, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/graalvm-jdk-21/Contents/Home
Default locale: zh_CN_#Hans, platform encoding: UTF-8
OS name: "mac os x", version: "26.2", arch: "x86_64", family: "mac"

######################### 切换到17

╭─░▒▓  │  ~/software  ❯ jenv local 17
╭─░▒▓  │  ~/software  ❯ java -version
java version "17.0.12" 2024-07-16 LTS
Java(TM) SE Runtime Environment Oracle GraalVM 17.0.12+8.1 (build 17.0.12+8-LTS-jvmci-23.0-b41)
Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 17.0.12+8.1 (build 17.0.12+8-LTS-jvmci-23.0-b41, mixed mode, sharing)

╭─░▒▓  │  ~/software  ❯ mvn -v
Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1)
Maven home: /Users/xincan/software/maven/apache-maven-3.9.12
Java version: 17.0.12, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/graalvm-jdk-17/Contents/Home
Default locale: zh_CN_#Hans, platform encoding: UTF-8
OS name: "mac os x", version: "26.2", arch: "x86_64", family: "mac"

╭─░▒▓  │  ~/software  ❯  mvnd -v
Apache Maven Daemon (mvnd) 1.0.3 darwin-amd64 native client (824a1fd42088e27dec6cc7cc392b9122379e7bf0)
Terminal: org.jline.terminal.impl.PosixSysTerminal with pty org.jline.terminal.impl.jni.osx.OsXNativePty
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /Users/xincan/software/maven/maven-mvnd-1.0.3-darwin-amd64/mvn
Java version: 17.0.12, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/graalvm-jdk-17/Contents/Home
Default locale: zh_CN_#Hans, platform encoding: UTF-8
OS name: "mac os x", version: "26.2", arch: "x86_64", family: "mac"

最后, 整体还是比较丝滑的

五、番外篇

  1. mvnd建议配置
    • /Users/xincan/software/maven/maven-mvnd-1.0.3-darwin-amd64/conf/mvnd.properties, 最后增加自定义mvn.settings配置
properties 复制代码
maven.settings=/Users/xincan/software/maven/maven-mvnd-1.0.3-darwin-amd64/mvn/conf/settings.xml
  • /Users/xincan/software/maven/maven-mvnd-1.0.3-darwin-amd64/mvn/conf/settings.xml
  • 这里, 自定义localRepository的路径
  • 配置多个jdk版本, activeProfiles默认设置
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.2.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  <localRepository>/Users/xincan/software/maven/repository</localRepository>
  -->

  <localRepository>/Users/xincan/software/maven/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
     | 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>
    -->
    <server>
      <id>xincan-snapshots</id>
      <username>admin</username>
      <password>xincan-0818</password>
    </server>
    <server>
      <id>xincan-releases</id>
      <username>admin</username>
      <password>xincan-0818</password>
    </server>
    <server>
      <id>xincan-public</id>
      <username>admin</username>
      <password>xincan-0818</password>
    </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>xincan-public</id>
      <name>xincan-public</name>
      <url>http://localhost:8081/nexus/repository/xincan-public/</url>
      <mirrorOf>*</mirrorOf>
    </mirror>
    <mirror>
      <id>xincan-releases</id>
      <name>xincan-releases</name>
      <url>http://localhost:8081/nexus/repository/xincan-releases/</url>
      <mirrorOf>*</mirrorOf>
    </mirror>
    <mirror>
      <id>xincan-snapshots</id>
      <name>xincan-snapshots</name>
      <url>http://localhost:8081/nexus/repository/xincan-snapshots/</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>
    -->

    <!--
     | 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>
    -->

    <profile>
      <id>jdk-8</id> 
      <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <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>
    </profile>

    <profile>
      <id>jdk-11</id> 
      <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <maven.compiler.source>11</maven.compiler.source>
        <maven.compiler.target>11</maven.compiler.target>
        <maven.compiler.compilerVersion>11</maven.compiler.compilerVersion>
      </properties>
    </profile>

    <profile>
      <id>jdk-17</id> 
      <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <maven.compiler.source>17</maven.compiler.source>
        <maven.compiler.target>17</maven.compiler.target>
        <maven.compiler.compilerVersion>8</maven.compiler.compilerVersion>
      </properties>
    </profile>

    <profile>
      <id>jdk-21</id> 
      <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <maven.compiler.source>21</maven.compiler.source>
        <maven.compiler.target>21</maven.compiler.target>
        <maven.compiler.compilerVersion>21</maven.compiler.compilerVersion>
      </properties>
    </profile>

    <profile>
      <id>jdk-25</id> 
      <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <maven.compiler.source>25</maven.compiler.source>
        <maven.compiler.target>25</maven.compiler.target>
        <maven.compiler.compilerVersion>25</maven.compiler.compilerVersion>
      </properties>
    </profile>

    <profile>
      <id>nexus-server</id>
      <repositories>
        <repository>
          <id>central</id>
          <url>http://localhost:8081/nexus/repository/xincan-public/</url>
          <releases>
            <enabled>true</enabled>
            <updatePolicy>always</updatePolicy>
          </releases>
          <snapshots>
            <enabled>true</enabled>
            <updatePolicy>always</updatePolicy>
          </snapshots>
          </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>central</id>
          <url>http://localhost:8081/nexus/repository/xincan-public/</url>
          <releases>
	    <enabled>true</enabled>
	    <updatePolicy>always</updatePolicy>
          </releases>
          <snapshots>
            <enabled>true</enabled>
            <updatePolicy>always</updatePolicy>
          </snapshots>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>

  <activeProfiles>
    <activeProfile>jdk-21</activeProfile>
    <activeProfile>nexus-server</activeProfile>
  </activeProfiles>
 
</settings>
  • 在用目录下创建文件
  • ~/.mvnd/mvnd.properties
shell 复制代码
╭─░▒▓  │  ~/software  ❯ cat ~/.mvnd/mvnd.properties
# 设定JDK, ($JAVA_HOME, 会随着jenv的版本切换而切换, 上述验证过)
mvnd.java.home=$JAVA_HOME
# 强制 Mvnd 使用你自定义的 settings.xml
maven.settings=/Users/xincan/software/maven/maven-mvnd-1.0.3-darwin-amd64/mvn/conf/settings.xml
# 显式指定本地仓库路径, 避免第三方包被下载到~/.m2/repository下,(个人补习费放到此路径)
mvnd.localRepository=/Users/xincan/software/maven/repository
相关推荐
派大鑫wink2 小时前
【Day13】集合框架(一):List 接口(ArrayList vs LinkedList)实战
java·开发语言·windows
眠りたいです2 小时前
Docker:镜像的运行实体-Docker Container
java·运维·c++·docker·容器·eureka
斌将军2 小时前
如何在MAC的eclipse中根据win11虚拟机的SAPGUI登录配置创建ABAP project
macos·eclipse
sunshine__sun2 小时前
【Mac安装|更换chromedriver】
macos
Filotimo_2 小时前
在java后端开发中,ES的用处
java·elasticsearch·jenkins
TheNextByte12 小时前
如何轻松地将音乐从Mac传输到Android ?
android·stm32·macos
华仔啊2 小时前
都在用 Java8 或 Java17,那 Java9 到 16 呢?他们真的没用吗?
java·后端
WizLC2 小时前
【后端】面向对象编程是什么(附加几个通用小实例项目)
java·服务器·后端·python·设计语言
刘个Java2 小时前
手搓遥控器通过上云api执行航线
java·redis·spring cloud·docker