Centos7 搭建 Maven私服Nexus

大板鲫

已于 2023-01-16 15:56:26 修改

阅读量2.3k

点赞数 2

文章标签： maven java

于 2021-11-30 21:48:24 首次发布

本文链接：https://blog.csdn.net/qq_41062545/article/details/121642715

版权

五、maven setting文件配置，pom.xml配置

前言

Maven私服是:公司在自己的局域网内搭建的 maven远程仓库服务器，每个员工的电脑上安装 maven 软件并且连接私服服务器，员工将自己开发的项目打成 jar 并发布到私服服务器，其它项目组就可以从私服服务器下载所依赖的组件（jar）

一、安装配置jdk

查询系统是否已安装jdk

rpm -qa|grep java

卸载已安装的jdk

rpm -e --nodeps java-1.8.0-openjdk-1.8.0.161-2.b14.el7.x86_64
rpm -e --nodeps java-1.8.0-openjdk-headless-1.8.0.161-2.b14.el7.x86_64
rpm -e --nodeps java-1.7.0-openjdk-1.7.0.171-2.6.13.2.el7.x86_64
rpm -e --nodeps java-1.7.0-openjdk-headless-1.7.0.171-2.6.13.2.el7.x86_64

验证是否已经卸载

rpm -qa|grep java
java -version

在usr下创建software目录 , 将 jdk-linux-x64.tar.gz 上传至该文件夹

mkdir /usr/software

解压 jdk-linux-x64.tar.gz

tar -zxvf /usr/software/jdk-linux-x64.tar.gz

配置JDK环境变量，编辑 /etc/profile 文件

vi /etc/profile

先将光标(可以使用快捷键Shift+g)移到最后一行，然后输入 i 进入编辑状态，粘贴如下内容，输入Esc 进入命令模式输入：wq! 保存修改信息

export JAVA_HOME=/usr/software/jdk1.8.0_131
export PATH=$JAVA_HOME/bin:$PATH

配置文件生效

source /etc/profile

测试 JDK 安装

java -version

二、搭建Maven

将 apache-maven-3.6.1-bin.tar.gz 上传至 /usr/software

解压 apache-maven-3.6.1-bin.tar.gz

tar -zxvf /usr/software/apache-maven-3.6.1-bin.tar.gz

配置Maven环境变量

vi /etc/profile

先将光标(可以使用快捷键Shift+g)移到最后一行，然后输入 i 进入编辑状态，粘贴如下内容，输入Esc 进入命令模式输入：wq! 保存修改信息

export JAVA_HOME=/usr/software/jdk1.8.0_131
export MAVEN_HOME=/usr/software/apache-maven-3.6.1
export PATH=$JAVA_HOME/bin:$MAVEN_HOME/bin:$PATH

配置文件生效

source /etc/profile

测试maven安装

mvn -version

三、搭建Nexus

将 nexus-3.9.0-01-unix.tar.gz 上传至 /usr/software

解压 nexus-3.9.0-01-unix.tar.gz

tar -zxvf nexus-3.9.0-01-unix.tar.gz

定位到nexus-3.9.0-01/bin目录下 , 修改nexus文件

# 先定位到usr/software目录下
cd /usr/software/nexus-3.9.0-01/bin/
# 修改nexus文件
vi nexus

修改文件的内容为:

run_as_user='root'
run_as_root=false

修改nexus-3.9.0-01/etc/nexus-default.properties配置表中属性

# Nexus服务监听的端口；
application-port=8081
# Nexus服务监听的主机；
application-host=0.0.0.0 
# Nexus服务的上下文路径
nexus-context-path=/

开放8081端口号

firewall-cmd --add-port=8081/tcp --permanent
firewall-cmd --reload

启动nexus

#使用cd命令 定义到/usr/software/nexus-3.20.1-01/bin目录下
cd /usr/software/nexus-3.20.1-01/bin
# 启动Nexus admin123
# ./nexus run
./nexus start

账号：admin 密码：admin123

四、批量上传jar包

1、先将本地maven/localrepository仓库打一个完整的zip压缩包，上传至/opt

2、解压localrepository.zip，进入/opt/localrepository目录

3、创建脚本 touch mavenimport.sh，写入以下内容；

#!/bin/bash
# copy and run this script to the root of the repository directory containing files
# this script attempts to exclude uploading itself explicitly so the script name is important
# Get command line params

while getopts ":r:u:p:" opt; do
	case $opt in
		r) REPO_URL="$OPTARG"
		;;
		u) USERNAME="$OPTARG"
		;;
		p) PASSWORD="$OPTARG"
		;;
	esac
done

find . -type f -not -path './mavenimport\.sh*' -not -path '*/\.*' -not -path '*/\^archetype\-catalog\.xml*' -not -path '*/\^maven\-metadata\-local*\.xml' -not -path '*/\^maven\-metadata\-deployment*\.xml' | sed "s|^\./||" | xargs -I '{}' curl -u "$USERNAME:$PASSWORD" -X PUT -v -T {} ${REPO_URL}/{} ;

4、输入chmod a+x mavenimport.sh进行可执行授权

chmod a+x mavenimport.sh

5、执行导入命令 (注意：将地址换成自己的私服地址)

./mavenimport.sh -u admin -p admin123 -r http://ip:8081/repository/maven-releases/

五、maven setting文件配置，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.home}/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>D:\JAVA\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>nexus-releases</id>
            <username>admin</username>
            <password>admin123</password>
        </server>
        <server> 
            <id>nexus-snapshots</id>
            <username>admin</username>
            <password>admin123</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>nexus</id>  
          <mirrorOf>*</mirrorOf>  
          <url>http://192.168.31.148:8081/repository/maven-public/</url>  
        </mirror>
 
		 
		<mirror>
		  <id>alimaven</id>
		  <name>aliyun maven</name>
		  <url>http://maven.aliyun.com/nexus/content/groups/public/</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>
    -->

    <!--
     | 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>nexus</id>  
          <!--指定仓库-->
          <repositories>  
            <repository>  
              <id>my-repo</id>  
              <url>http://192.168.31.148:8081/repository/my-repo/</url>  
              <releases><enabled>true</enabled></releases>  
              <snapshots><enabled>true</enabled></snapshots>  
            </repository>  
          </repositories>  
          <!--指定插件仓库-->
         <pluginRepositories>  
            <pluginRepository>  
              <id>my-repo</id>  
              <url>http://192.168.31.148:8081/repository/my-repo/</url>  
              <releases><enabled>true</enabled></releases>  
              <snapshots><enabled>true</enabled></snapshots>  
            </pluginRepository>  
          </pluginRepositories>  
        </profile> 
 
 
  </profiles>
  
    <activeProfiles>
        <activeProfile>nexus</activeProfile>
    </activeProfiles>
  

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

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

大板鲫

关注

2
点赞
踩
7

收藏

觉得还不错? 一键收藏
0
评论
Centos7 搭建 Maven私服Nexus

前言Maven私服是:公司在自己的局域网内搭建的 maven远程仓库服务器，每个员工的电脑上安装 maven 软件并且连接私服服务器，员工将自己开发的项目打成 jar 并发布到私服服务器，其它项目组就可以从私服服务器下载所依赖的组件（jar）一、安装配置jdk查询系统是否已安装jdk#rpm -qa|grep java卸载已安装的jdk#rpm -e --nodeps java-1.8.0-openjdk-1.8.0.161-2.b14.el7.x86_64#r...
复制链接

扫一扫