一、maven的安装及配置

1、下载Maven

官方下载地址：

下载并解压

2、配置环境变量

添加新的系统环境变量MAVEN_HOME， 并设置其值为你安装的目录

      MAVEN_HOME= D:\Maven\apache-maven-3.3.3-bin\apache-maven-3.3.3

更新系统PATH 变量， 添加;%MAVEN_HOME%\bin;到尾部

3、测试maven配置是否成功

（安装maven前请确保已安装JDK并成功配置其环境变量）

打开命令行窗口，输入mvn -v，

如果有maven 版本信息输出则证明配置成功，否则请查看自己配置路径等是否正确。

二、nexus私服的搭建

1.下载  

http://www.sonatype.org/nexus/go

这里我们下载window 环境下的nexus文件 

http://www.sonatype.org/downloads/nexus-2.1.1-bundle.zip

 

2.安装和启动服务 

下载完成后，在盘符上新建nexus 文件夹，将 

nexus-2.1.1-bundle.zip解压到nexus目录中。 

 

3、配置环境变量 

NEXUS_HOME=D:\Maven\nexus-2.11.1-01-bundle\nexus-2.11.1-01

PATH 添加 %NEXUS_HOME%\bin;%NEXUS_HOME%\bin\jsw\windows-x86-64；

 

4、执行nexus 服务安装   

nexus install 服务安装成功后    

  nexus start 启动nexus服务 

会报如下错误

修改D:\Maven\nexus-2.11.1-01-bundle\nexus-2.11.1-01\bin\jsw\conf的wrapper.conf文件

要用管理员权限打开命令行窗口

成功

5、地址栏上输入 

http://localhost:8081/nexus

如果到此处，都一切正常说明，你成功了！ 

默认用户名admin,密码为admin123 

6、私服的仓库配置

maven的D:\Maven\apache-maven-3.3.3-bin\apache-maven-3.3.3\conf\settings.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

   

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="           xmlns:xsi="           xsi:schemaLocation=" >   <!-- 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:/MavenRepository/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>user-snapshots</id>       <username>deployment</username>       <password>deployment123</password>     </server>

    <server>

      <id>user-releases</id>       <username>deployment</username>       <password>deployment123</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>central</id>       <mirrorOf>*</mirrorOf>       <name>Human Readable Name for this Mirror.</name>       <url></url>     </mirror>     <!-- 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></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>central-repos</id>       <repositories>         <repository>           <id>central</id>           <name>Central</name>           <url></url>           <releases>             <enabled>true</enabled>         </releases>           <snapshots>                 <enabled>true</enabled>          </snapshots>         </repository>       </repositories>     </profile>     <!-- 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></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>     -->   </profiles> <activeProfiles>     <activeProfile>central-repos</activeProfile>   </activeProfiles>   <!-- activeProfiles    | List of profiles that are active for all builds.    |   <activeProfiles>     <activeProfile>alwaysActiveProfile</activeProfile>     <activeProfile>anotherAlwaysActiveProfile</activeProfile>   </activeProfiles>   --> </settings>