以前一直用舊點的版本，今天（五一放假）整理來了下自己的軟件，然后更新了下重要的兩個：maven和nexus。

這里簡單記錄下自己的配置，用的都是最新的版本（截止到2015-05-02）：

首先寫一下nexus的配置，因為我覺得先配置nexus再配置maven更方便，這樣maven也不會直接到中央倉庫下載jar包，下面是nexus的配置，就改兩個地方：

1、配置java環境，最好jdk1.7以上的版本，理由是等下的maven3.3.3必須是jdk1.7以上才可以用。

配置文件路徑：E:\MySoftware\nexus2.11.1-01\nexus-2.11.1-01\bin\jsw\conf\wrapper.conf

修改：找到大概15行的地方wrapper.java.command=java，改為wrapper.java.command=C:\Program Files (x86)\Java\jdk1.7.0_72\bin\java，也就是jdk的路徑

2、配置jetty的端口，由于我的nexus是直接使用內置的jetty服務器，而且我的window7系統的8081端口被占用了，也不知道是哪個軟件占用的，所以直接修改jetty的端口為8181，

修改文件路徑：E:\MySoftware\nexus2.11.1-01\nexus-2.11.1-01\conf\nexus.properties

修改：找到application-port=8081這一句，直接修改端口為8181

修改好nexus的配置后就可以安裝了，安裝前，我把nexus的E:\MySoftware\nexus2.11.1-01\nexus-2.11.1-01\bin目錄添加到了系統的環境變量path中。然后在命令行進入到nexus的bin目錄，運行一下命令安裝nexus的服務：

1、nexus install   安裝服務

2、nexus start  啟動服務，其實就是啟動jetty

如果啟動成功會顯示start successful，這時候在瀏覽器輸入：http://localhost:8181/nexus/   就可以看到nexus的界面了，登陸使用默認用戶及密碼：admin和admin123，登陸以后可以配置更多的nexus選項，我這里只要增加了一下代理倉庫的地址，倉庫的地址我單獨寫了一篇文章記錄，nexus的倉庫說明網上有很多，我這里不說了。上幾張圖吧

配置好nexus之后就配置maven，配置很簡單：

1、把maven的E:\MySoftware\apache-maven-3.3.3\bin目錄加到系統的path中。

2、配置文件：E:\MySoftware\apache-maven-3.3.3\conf\settings.xml （maven的全局配置文件，所有用戶都起作用）

文件內容：

<pre name="code" class="html"><?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>/path/to/local/repo</localRepository>
  -->
 <!-- 配置倉庫下載的jar包存放路徑，這里設置的是使用系統環境變量的設置，
		方便maven放在那里，jar包就直接保存在那里。這里就是保存在maven目錄下的repos文件夾 -->
<localRepository>${M2_HOME}/repos</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>
    -->
		<!-- 使用本地tomcat配置 -->
		<server> 
		   <id>tomcat7</id> 
		   <username>admin</username> 
		   <password>admin</password> 
		</server>
		
		<!-- 上傳到hosted庫的用戶設置 -->
		<server>
		    <id>user-release</id>
		    <username>admin</username>
		    <password>admin123</password>
		</server>
		<server>
		    <id>user-snapshot</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
     | 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>
     -->
	 <!-- 設置全局鏡像，所有下載從nexus下載 -->
	<mirror>
		<id>nexus-public</id>
		<name>nexus-public</name>
		<mirrorOf>*</mirrorOf>
		<url>http://localhost:8181/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
     | 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>
    -->
	<!-- 配置maven建立的項目時使用jdk1.7 -->
	<profile>
		<id>jdk-1.7</id>
		<activation>
			<activeByDefault>true</activeByDefault>
			<jdk>1.7</jdk>
		</activation>
		<properties>
			<maven.compiler.source>1.7</maven.compiler.source>
			<maven.compiler.target>1.7</maven.compiler.target>
			<maven.compiler.compilerVersion>1.7</maven.compiler.compilerVersion>
		</properties>
	</profile>
	
	<!-- 配置倉庫，此處配置倉庫沒什么作用了，上面配置了全局的鏡像地址，但是網上都這么寫，我也就跟著寫了。 -->
	<profile>
        <id>nexus</id>
        <repositories>

            <repository>
				<id>nexus-public</id>
				<name>nexus public repository</name>
				<url>http://nexus-public</url>
				<releases>
					<enabled>true</enabled>
				</releases>
				<snapshots>
					<enabled>true</enabled>
				</snapshots>
            </repository>

        </repositories>
		
		
		<pluginRepositories>    
            <pluginRepository>    
                <id>nexus-public</id>    
                <url>http://nexus-releases</url>    
                <releases><enabled>true</enabled></releases>    
                <snapshots><enabled>true</enabled></snapshots>    
            </pluginRepository>    
            <pluginRepository>    
                <id>nexus-public</id>    
                <url>http://nexus-snapshots</url>    
                <releases><enabled>true</enabled></releases>    
                <snapshots><enabled>true</enabled></snapshots>    
            </pluginRepository>    
        </pluginRepositories> 
     </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
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
	<!-- 激活配置 -->
	<activeProfiles>
		<activeProfile>nexus</activeProfile>
	</activeProfiles>
</settings>