2. 程式人生 > 實用技巧 >私有Maven倉庫安裝和使用

私有Maven倉庫安裝和使用

阿新 • • 發佈：2020-12-09

安裝

這裡選擇安裝的是windows平臺，linux安裝類似，下載可能要梯子

官網下載頁

https://help.sonatype.com/repomanager2/download

下載連結

https://download.sonatype.com/nexus/oss/nexus-latest-bundle.zip

這裡下載2.X的最新版本 捆綁包，內建jetty容器，可作為獨立服務執行，jdk 要求1.8

（個人覺得 2.x版本更好用）

下載解壓後，可以看到兩個目錄

安裝： （這裡以本機安裝作為示例）

管理員身份進入解壓後的bin目錄下，執行 nexus 命令可以看到 提示命令

執行 nexus install ,等待安裝完成

執行 nexus start 啟動 nexus

訪問 http://127.0.0.1:8081/nexus ,看到該頁面即表示正常啟動

基礎使用

登入

右上角點選登入 admin/admin123 （初始預設賬號密碼）

建立 my-maven-release 和 my-maven-snapshot

（名字自定義）,作為穩定版和快照版私有倉庫

兩個倉庫type都是 hosted 型別

my-maven-release

建立 my-maven-snapshot ,把 Repository Policy 改為Snapshot

至此，倉庫已經建立完畢

nexus中所有倉庫的實際位置都儲存在

nexus-2.14.19-01-bundle\sonatype-work\nexus\storage 目錄下

部署專案到私有庫

開啟一個maven專案

在pom.xml新增以下內容

<distributionManagement>

    <repository>

        <id>my-maven-releases</id>

        <url>http://127.0.0.1:8081/nexus/content/repositories/my-maven-releases</url>

    </repository>

    <snapshotRepository>

        <id>my-maven-snapshot</id>

        <url>http://127.0.0.1:8081/nexus/content/repositories/my-maven-snapshot</url>

    </snapshotRepository>

</distributionManagement>

內容來源於剛才建立的倉庫

maven的setting.xml中配置 server,因為訪問倉庫需要賬號密碼

<server>  

    <id>my-maven-releases</id>  

    <username>admin</username>  

    <password>admin123</password>  

</server>  

<server>  

    <id>my-maven-snapshot</id>  

    <username>admin</username>  

    <password>admin123</password>  

</server>

　　

maven專案下執行 mvn deploy

或者使用IDE 的maven外掛執行clean deploy

deploy成功之後可以看到nexus遠端倉庫有了相關的jar包資訊，本地maven倉庫 org.example 資料夾下也會出現相關jar包

直接上傳jar包到私有maven庫

配置完成後，選擇檔案，點選 Add Artifact , 最後點選上傳

更改nexus 倉庫平臺 賬號密碼

或者點選 User ,選中右鍵

Nexus OSS 修改 埠號

開啟 conf 資料夾下的 nexus.properties 檔案

從私有倉庫拉取依賴

配置公共庫

將右邊配置的倉庫移動到左邊並儲存 ，就可以在公共庫下看到之前deploy的專案的相關資訊

這邊也可以新增aliyun代理倉庫並把它移動到公共庫下，

這樣個人的setting.xml 阿里雲 映象配置都可以省略了

但是如果不是公司網路，就會下不了依賴，個人可去可不去

setting.xml配置

servers部分 （這邊如果不需要上傳專案到私有倉庫，可以不需要配置）

	</servers>		
                <server>   
			<id>my-maven-releases</id>   
			<username>admin</username>   
			<password>admin123</password>   
		</server>   
		<server>   
			<id>my-maven-snapshot</id>   
			<username>admin</username>   
			<password>admin123</password>   
		</server>
	</servers>

Mirrors部分 用aliyun的maven倉庫，可以不用變

私有倉庫配置部分

<profiles>
    <profile>
		<id>my-maven</id>
		<repositories>
			<repository>
				<id>public</id>
				<name>public Repository</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
				<releases>
					<enabled>true</enabled>
				</releases>
				<snapshots>
					<enabled>true</enabled>
				</snapshots>
			</repository>
		</repositories>
		<pluginRepositories>
			<pluginRepository>
				<id>public</id>
				<name>Public Repositories</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
			</pluginRepository>
		</pluginRepositories>
	</profile>
	
  </profiles>　

記得啟用配置

	<activeProfiles>
		<activeProfile>my-maven</activeProfile>
	</activeProfiles>

完整的配置如下：

<?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\Apache Software Foundation\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>my-maven-releases</id>   
			<username>admin</username>   
			<password>admin123</password>   
		</server>   
		<server>   
			<id>my-maven-snapshot</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>mynexus</id>
		<name>mynexus maven</name>
		<url>http://localhost:8081/nexus/content/groups/public/</url>
		<mirrorOf>*</mirrorOf>        
	</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>my-maven</id>
		<repositories>
			<repository>
				<id>public</id>
				<name>public Repository</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
				<releases>
					<enabled>true</enabled>
				</releases>
				<snapshots>
					<enabled>true</enabled>
				</snapshots>
			</repository>
		</repositories>
		<pluginRepositories>
			<pluginRepository>
				<id>public</id>
				<name>Public Repositories</name>
				<url>http://127.0.0.1:8081/nexus/content/groups/public/</url>
			</pluginRepository>
		</pluginRepositories>
	</profile>
	
  </profiles>

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

　　

相關推薦

私有Maven倉庫安裝和使用

安裝 這裡選擇安裝的是windows平臺，linux安裝類似，下載可能要梯子 官網下載頁

Docker 安裝私有映象倉庫 Registry 和 視覺化映象管理工具 docker-registry-ui

安裝私有映象倉庫 下載Registry的Docker映象 docker pull registry:2 使用Docker容器執行Registry服務，需要新增環境變數REGISTRY_STORAGE_DELETE_ENABLED=true開啟刪除映象的功能；

maven倉庫repositories和mirrors的配置及區別詳解

maven倉庫配置 倉庫優先順序為：本地倉庫(localRepositories) > profile中的repositories倉庫 > POM > mirrors全域性倉庫

搭建公司私有MAVEN倉庫的方法

使用工具及環境： cent os 7; jdk 1.8; nexus-3.9.0-01-unix.tar.gz 安裝： 首先，下載安裝包：https://sonatype-download.global.ssl.fastly.net/nexus/3/nexus-3.9.0-01-unix.tar.gz

Maven的安裝和settings.xml的配置

技術標籤：JAVAmavenjava Maven的安裝和settings.xml的配置 1 Maven的安裝2 配置Maven的環境資訊

Windows下maven的安裝和配置

一、maven的安裝略 二、maven配置，使用阿里源 編輯maven安裝目錄下的conf/settings.xml，新增如下配置：

使用maven工具安裝第三方jar包到本地倉庫和私服

1. 如何安裝第三方jar包到本地倉庫 第一種方式：用window黑視窗進入到本地第三方 jar 所在的目錄，執行如下命令。

使用maven命令安裝jar包到本地倉庫的方法步驟

第三方jar包在開發工具中引入後編譯沒問題,啟動除錯包括打包時會提示找不到jar包的錯誤.需要上傳到maven倉庫中,並在pom檔案內引入.

怎麼把本地jar包放入本地maven倉庫和遠端私服倉庫

1.將本地jar包放入本地倉庫。只需執行如下命令即可： mvn install:install-file -Dfile=D:/demo/fiber.jar -DgroupId=com.sure -DartifactId=fiber -Dversion=1.0 -Dpackaging=jar

使用maven命令安裝jar包到本地倉庫

第三方jar包在開發工具中引入後編譯沒問題, 啟動除錯包括打包時會提示找不到jar包的錯誤.需要上傳到maven倉庫中,並在pom檔案內引入.

k8s搭建安裝 Harbor 私有映象倉庫（詳細）

一、設定主機名（可忽略） # 設定 Harbor 伺服器主機名 hostnamectl set-hostname harbor.wangzy.com

Maven倉庫無用檔案和資料夾清理的方法實現

眾所周知，隨著經濟社會的發展，我們的物質生活…不好意思，走錯片場了…

maven安裝和設定-windows系統

技術標籤：JAVA開發環境設定maven 1、需先安裝jdk（版本要求參見maven對應版本要求）

【docker容器入門（四）】： Docker 私有映象倉庫registry安裝

registry是docker官方提供的私有映象倉庫。便於我們管理私有映象。 部署registry 1. 啟動私有映象倉庫registry容器

maven在linux和windows平臺下的安裝教程

技術標籤：javalinuxmaven 本文是maven系列教程第一篇，包含maven的概念介紹、linux平臺下的安裝和windows平臺下的安裝，請根據自己電腦系統學習對應的內容

Android Studio 關聯Module打包成aar和使用本地Maven倉庫

技術標籤：Android StudioSDKandroid studiosdkaar 關聯Module打包成aar(建立Maven專案) 理清自己的專案依賴關係專案中兩個Module（Interact和JsBridge）需要製作成aar;其中 Interact依賴JsBridge.按照專案依賴

docker 私有倉庫搭建和測試

簡介 Docker私有倉庫主要是企業內部用來存放映象的倉庫，相對官方倉庫以及阿里雲倉庫，具有更高的保密安全級別

上傳元件jar和原始碼到maven倉庫

操作 在父級pom中新增 <distributionManagement> <snapshotRepository> <id>sge</id>//這個位置的id需要和maven的settings.xml檔案中想匹配

git在windows的安裝和關聯遠端倉庫的基本使用

技術標籤：技術專欄git 安裝（windows） 1.官網下載對應的版本，然後按預設選項安裝即可。安裝完成後，在開始選單裡找到“Git”->“Git Bash”，蹦出一個類似命令列視窗的東西，就說明Git安裝成功！

java Gradle安裝和設定本地倉庫

Gradle安裝 下載地址:https://gradle.org/配置環境變數 新增GRADLE_HOME設定path: %GRADLE_HOME%/bingradle -v, 出現如下介面,表示安裝成功.