maven使用nexus3在windows下搭建私服

最新推荐文章于 2021-05-17 00:30:26 发布

qile奇乐

最新推荐文章于 2021-05-17 00:30:26 发布

阅读量342

点赞数

分类专栏： nexus 文章标签： nexus

本文链接：https://blog.csdn.net/qile0772/article/details/89221389

版权

nexus 专栏收录该内容

1 篇文章 0 订阅

订阅专栏

一、下载nexus3

下载地址：https://www.sonatype.com/download-oss-sonatype

这里下载的是nexus-3.15.2-01-win64.zip。

二、解压

将下载好的nexus解压到指定目录，这里我的解压路径为：D:\Program Files\nexus-3.15.2-01。

三、启动服务

1.命令行启动（注意该方式启动，关闭命令行窗口后，服务停止）：

nexus.exe /run

2.服务方式启动：

nexus.exe /install

可能出现权限不足提示：

D:\Program Files\nexus-3.15.2-01\nexus-3.15.2-01\bin>nexus.exe /install
Could not open SCManager.

可以通过管理员方式运行cmd窗口。

安装服务成功后，可以通过命令行启动服务：net start nexus。也可以通过任务管理器查找nexus服务，右键运行。

四、登录nexus

nexus默认账号/密码：admin/admin123

如果未改变nexus服务默认监听端口的话，则登录地址为：http://localhost:8081。

监听端口的修改为：nexus-3.15.2-01\etc\nexus-default.properties

主要内容如下：

application-host : Nexus服务监听的主机
application-port: Nexus服务监听的端口，
nexus-context-path : Nexus服务的上下文路径

我这里修改的端口为8989。登录成功节目如下：

主要仓库有：

主要仓库介绍：

maven-central：maven中央仓库

maven-releases：发行私库

maven-snapshots：快照私库

maven-public：仓库分组，把上面三个仓库组合在一起对外提供服务，在本地maven基础配置settings.xml中使用。

仓库类型：

hosted（宿主仓库库）：存放本公司开发的jar包（正式版本、测试版本）

proxy（代理仓库）：代理中央仓库、Apache下测试版本的jar包

group（组仓库）：使用时连接组仓库，包含Hosted（宿主仓库）和Proxy（代理仓库）

virtual (虚拟仓库)：基本用不到，重点关注上面三个仓库的使用

五、添加代理库

Create repository->maven2(proxy)

1、分别创建aliyun、UK、jboss三个代理仓库：

2、把这三个代理仓库添加到maven-public分组中：

六、配置setting文件

附上setting文件：

<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 (x86)\apache-maven-3.3.9\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>
    -->
  <!--配置本地镜像仓库的登录名及密码，避免maven发布jar到本地仓库时报401无权限错误码 -->
  <server>  
    <id>local-szyh</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>
     -->
    <!--配置远程镜像仓库及其url -->
	<mirror>
		<id>nexus-aliyun</id>
		<name>Nexus aliyun</name>
		<url>http://maven.aliyun.com/nexus/content/groups/public/</url>
		<mirrorOf>central</mirrorOf>
	</mirror>
	<mirror>
      <id>repo2</id>
      <name>Mirror from Maven Repo2</name>
      <url>http://repo2.maven.org/maven2/</url>
      <mirrorOf>central</mirrorOf>
	</mirror>
	<mirror>
      <id>ui</id>
      <name>Mirror from UK</name>
      <url>http://uk.maven.org/maven2/</url>
      <mirrorOf>central</mirrorOf>
	</mirror>
	<mirror>
      <id>jboss-public-repository-group</id>
      <mirrorOf>central</mirrorOf>
      <name>JBoss Public Repository Group</name>
      <url>http://repository.jboss.org/nexus/content/groups/public</url>
	</mirror>
	<mirror>
      <id>local-szyh</id>
      <mirrorOf>local</mirrorOf>
      <name>szyh</name>
      <url>http://localhost:8989/repository/maven-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
     | 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用来确定该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>
   </profile>
	
	<profile>
        <id>local-szyh</id>
		<!-- 远程仓库列表 配置本地发行及快照仓库，以便发布的jar能被其他工程下载引用 -->
        <repositories>
            <repository>
                <id>public</id>
				<!-- 虚拟的URL形式,指向镜像的URL-->
			    <url>http://localhost:8989/repository/maven-public/</url>
				<!-- 表示可以从这个仓库下载releases版本的构件-->
                <releases>
                    <enabled>true</enabled>
				    <updatePolicy>always</updatePolicy>
                </releases>
				<!-- 表示可以从这个仓库下载snapshot版本的构件 -->
                <snapshots>
                    <enabled>true</enabled>
			        <updatePolicy>always</updatePolicy>
                </snapshots>
            </repository>
        </repositories>

		<!-- 插件仓库列表 -->
		<pluginRepositories>
            <pluginRepository>
            <id>public</id>
            <url>http://localhost:8989/repository/maven-public/</url>
            <releases>
                <enabled>true</enabled>
                <updatePolicy>always</updatePolicy>
            </releases>
            <snapshots>
                <enabled>true</enabled>
                <updatePolicy>always</updatePolicy>
            </snapshots>
			</pluginRepository>
		</pluginRepositories>
    </profile>
  </profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
  <activeProfiles>
	<!--需要激活 <profile>中的ID才生效-->
	<activeProfile>jdk-1.8</activeProfile>
    <activeProfile>local-szyh</activeProfile>
  </activeProfiles>
</settings>

配置完setting文件后，我们还需要在pom文件中添加如下配置，才可发布成功需要发布的jar：

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