maven项目配置私服

本文介绍了如何在Windows或Linux环境中安装并运行Nexus私服,以及如何配置项目和Maven的settings.xml文件来上传jar到私服。通过在项目中设置repository和snapshotRepository,指定仓库URL,然后在本地maven settings中配置仓库ID、用户名和密码,可以实现项目依赖的私有化存储。此外,还讲解了如何通过maven-deploy-plugin将jar及其源码一同部署到私服,便于其他项目引用。

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

1. 首先在windows 或者在Linux服务器中安装并运行nexus私服。

2. 使用私服就是将项目jar 上传到私服中,提供给别的项目使用,那么就需要在项目中和maven的配置文件中配置文件

3. 项目中配置私服的仓库地址

 <distributionManagement>
        <repository>
            <id>maven-releases</id>
            <name>Nexus Release Repository</name>
            <url>http://192.168.121.131:8081/repository/maven-releases/</url>
        </repository>
        <snapshotRepository>
        <id>maven-snapshots</id>
            <name>Nexus Snapshot Repository</name>
            <url>http://192.168.121.131:8081/repository/snapshots/</url>
        </snapshotRepository>
    </distributionManagement>

4. 在本地的maven settings 配置文件需要配置如下:

<?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>D:\java\nexus_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>
        <id>maven-public</id>
        <username>admin</username>
        <password>admin</password>
    </server>
     <server>
        <id>maven-releases</id>
        <username>admin</username>
        <password>admin</password>
    </server>
     <server>
        <id>maven-snapshots</id>
        <username>admin</username>
        <password>admin</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>
      <id>nexus</id>
      <name>nexus</name>
      <mirrorOf>local</mirrorOf>
      <url>http://192.168.121.131:8083/repository/maven-public/</url>
    </mirror>
    <mirror>
      <id>alimaven</id>
      <mirrorOf>central</mirrorOf>
      <name>aliyun maven</name>
      <url>http://maven.aliyun.com/nexus/content/groups/public/</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>
      <id>nexus</id>
      <repositories>
        <repository>
          <id>nexus</id>
          <url>http://192.168.121.131:8081/nexus/content/groups/public</url>
          <releases>
            <enabled>true</enabled>
          </releases>
        </repository>
         <repository>
          <id>nexus-aliyun</id>
          <url>http://maven.aliyun.com/nexus/content/groups/public</url>
          <releases>
            <enabled>true</enabled>
          </releases>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>central</id>
          <url>http://maven.aliyun.com/nexus/content/groups/public</url>
          <releases>
            <enabled>true</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

注意: 项目中的pom文件配置的仓库ID要和maven settings 中 server 标签中的仓库id对应。

然后直接使用maven的deploy插件直接将项目jar包推到私服仓库中。

补充:

如果需要将jar的source 一并推到私服,需要在pom中的plugin标签下添加如下配置:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-source-plugin</artifactId>
                <executions>
                    <execution>
                        <id>attach-sources</id>
                        <goals>
                            <goal>jar</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

再次deploy的时候,就会将source一起打包上传到私服中去了,也方便引用方查看源码注释

### 如何在 Maven配置私有镜像与远程仓库 #### 私有镜像的配置 为了使 Maven 使用私有镜像,需要修改 `settings.xml` 文件中的 `<mirrors>` 节点。通过定义一个 `<mirror>` 条目来指向私有镜像服务器的位置[^2]。 以下是具体的配置方式: ```xml <mirrors> <mirror> <!-- 这是一个唯一标识符 --> <id>private-mirror</id> <!-- 镜像名称 --> <name>Private Mirror Repository</name> <!-- 定义该镜像是哪个远程仓库的替代品 --> <url>http://your-private-repo-url/repository/maven-public/</url> <!-- 替代所有的远程仓库 --> <mirrorOf>*</mirrorOf> </mirror> </mirrors> ``` 上述代码片段中,`<url>` 是私有镜像的具体 URL 地址,而 `<mirrorOf>*` 表示此镜像会覆盖所有其他远程仓库请求。 #### 远程仓库的配置 如果某些依赖项不在 Maven 的中央仓库中,则可以通过设置自定义的远程仓库地址解决这个问题。这同样是在 `pom.xml` 或者全局的 `settings.xml` 文件中完成的[^3]。 对于项目级别的配置,在项目的 `pom.xml` 文件中添加如下内容即可: ```xml <repositories> <repository> <id>remote-repository</id> <name>Remote Repository</name> <url>http://your-remote-repo-url/repository/maven-public/</url> </repository> </repositories> ``` 而对于全局范围内的配置(适用于所有项目),则需编辑 Maven 主目录下的 `settings.xml` 文件,并加入类似的结构到其中的 `<profiles>` 下面: ```xml <profile> <id>custom-profile</id> <repositories> <repository> <id>remote-repository-global</id> <name>Global Remote Repository</name> <url>http://your-remote-repo-url/repository/maven-public/</url> </repository> </repositories> </profile> <!-- 启用 profile --> <activeProfiles> <activeProfile>custom-profile</activeProfile> </activeProfiles> ``` 以上操作完成后,Maven 将会在构建过程中自动尝试从所指定的新位置获取所需的构件和插件。 #### 环境变量的重要性 另外需要注意的是,确保已经正确设置了 Maven 的环境变量 `MAVEN_HOME` 和将其 bin 目录路径添加至系统的 PATH 变量之中,这是运行任何 Maven 命令的前提条件之一[^1]。 ```bash export MAVEN_HOME=/path/to/your/apache-maven-directory export PATH=$PATH:$MAVEN_HOME/bin ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

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

余额充值