maven 通过nexus创建工厂的配置

访问中央工厂的地址：http://localhost:8081/nexus/index.html#welcome admin、admin123

查找到自己配置的maven仓库的位置，编辑setting.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: ~/.m2/repository

  <localRepository>/path/to/local/repo</localRepository>

  -->

	<localRepository>D:/workSoft/apache-maven-3.0.5-bin/maven仓库/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>

    -->

	<server>

      <id>user-release</id><!-- 与需要发布项目中pom.xml的<distributionManagement><repository><id>名字</id></repository> </distributionManagement>名字一致 -->

      <username>deployment</username>

      <password>deployment123</password>

    </server>

    <server>

      <id>user-snapshots</id><!-- 与需要发布项目中pom.xml的<distributionManagement><snapshotRepository><id>名字</id></snapshotRepository> </distributionManagement>名字一致 -->

      <username>deployment</username>

      <password>deployment123</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>

    -->

  </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>  </mirror>，才能够从网络中下载 -->

	<!-- 工厂的镜像，只要mirrorOf中的工厂要访问，都会自动来找镜像，

		如果镜像无法访问就不会再去中央工厂中查找，除非内部工厂开启 -->

	<!--  配置镜像 哪些工厂的id需要使用该镜像-->

	<mirror>

      <id>nexus</id>

	  <!-- 此时nexus和central将在该<url> </url>中查找

		<mirrorOf>nexus,central</mirrorOf>

	   -->

	   <!--

			*：表示所有的工厂都将从该url中查找，

			此时

				<profile>

					<id>nexusProfile</id>

					<repositories>

						<repository>

							<id>nexus</id>

							<name>Nexus Repository</name>

							<url>http://localhost:8081/nexus/content/groups/public/</url>

							<releases>

								<enabled>true</enabled>

							</releases>

							<snapshots>

								<enabled>true</enabled>

							</snapshots>

						</repository>

					</repositories>

				</profile>

				将变得毫无意义，

				也没有必要激活了，处理方法

				 <activeProfiles>

					<activeProfile></activeProfile>

				 </activeProfiles>

	   -->

	   <!-- 推荐做法 -->

	   <mirrorOf>*</mirrorOf>

      <name>Human Readable Name for this Mirror.</name>

	  <!-- 如果想链接特定的电脑作为工厂 ，就需要把loclhost改成相对应的ip地址，此时该ip对应的电脑才能作为工厂 -->

      <url>http://localhost:8081/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>

    -->

    <!--

     | 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>nexusProfile</id>

      <repositories>

        <repository>

          	<id>nexus</id>

			<name>Nexus Repository</name>

			<url>http://localhost:8081/nexus/content/groups/public/</url>

			<releases>

				<enabled>true</enabled><!-- 默认可以现在releases的jar包 -->

			</releases>

			<!-- snapshots:默认是关闭的，需要手动开启 -->

			<snapshots>

				<enabled>true</enabled><!-- 默认可以现在snapshots的jar包 -->

			</snapshots>

        </repository>

      </repositories>

    </profile>

	<profile>

      <id>centralProfile</id>

      <repositories>

        <repository>

          	<id>central</id>

			<name>Central Repository</name>

			<url>http://*</url>

			<layout> default </layout>

			<snapshots>

				<enabled>true</enabled><!-- snapshots开启，避免修改jar包里面的pom.xml的内容 -->

			</snapshots>

        </repository>

      </repositories>

    </profile>

  </profiles>

	<!--只有激活之后才生效,激活生效后，项目中的所有都可以使用了，就可以删除某项目中的父类文件中的<repositories></repositories> -->

    <activeProfiles>

		<activeProfile>nexusProfile</activeProfile>

		<activeProfile>centralProfile</activeProfile>

	</activeProfiles>

  <!-- activeProfiles

   | List of profiles that are active for all builds.

   |

  <activeProfiles>

    <activeProfile>alwaysActiveProfile</activeProfile>

    <activeProfile>anotherAlwaysActiveProfile</activeProfile>

  </activeProfiles>

  -->

</settings>

要发布项目的pom.xml文档配置user-parent

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

  <modelVersion>4.0.0</modelVersion>

  <groupId>zttc.itat.user</groupId>

  <artifactId>user-parent</artifactId>

  <version>0.0.1-SNAPSHOT</version>

  <packaging>pom</packaging>

  	<url>http://maven.apache.org</url>

  		  <!-- 导入了三个模块，吧这三个模块聚合在一起   聚合是模块的位置 -->

  <modules>

  	<module>../user-core</module>

  	<module>../user-log</module>

  	<module>../user-service</module>

  </modules>

  <!-- 项目发布 -->

  <distributionManagement>

  	<repository>

  		<id>user-release</id>

  		<name>user release resp</name>

  		<url>http://localhost:8081/nexus/content/repositories/releases/</url>

  	</repository>

  	<snapshotRepository>

  		<id>user-snapshots</id>

  		<name>user snapshots resp</name>

  		<url>http://localhost:8081/nexus/content/repositories/snapshots/</url>

  	</snapshotRepository>

  </distributionManagement>

	<properties>

		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

	</properties>

<!-- 	<repositories>

		只会在中央工厂中下载数据

		<repository>

			<id>nexus</id>

			<name>Nexus Repository</name>

			<url>http://localhost:8081/nexus/content/repositories/central/</url>

		</repository>

		内部开发的包能够被下载

		<repository>

			<id>nexus</id>

			<name>Nexus Repository</name>

			<url>http://localhost:8081/nexus/content/groups/public/</url>

			<releases>

				<enabled>true</enabled>默认可以现在releases的jar包

			</releases>

			snapshots:默认是关闭的，需要手动开启

			<snapshots>

				<enabled>true</enabled>默认可以现在snapshots的jar包

			</snapshots>

		</repository>

	</repositories> -->

	<dependencyManagement>

	  <dependencies>

	    <dependency>

			<groupId>org.eclipse.jetty</groupId>

			<artifactId>jetty-plus</artifactId>

			<version>9.2.0.M1</version>

		</dependency>

		<dependency>

			<groupId>junit</groupId>

			<artifactId>junit</artifactId>

			<version>4.10</version>

			<scope>test</scope>

		</dependency>

		<dependency>

			<groupId>org.hibernate</groupId>

			<artifactId>hibernate-core</artifactId>

			<version>4.1.10.Final</version>

		</dependency>

		<dependency>

			<groupId>mysql</groupId>

			<artifactId>mysql-connector-java</artifactId>

			<version>5.1.24</version>

			<scope>runtime</scope>

		</dependency>

		<dependency>

			<groupId>log4j</groupId>

			<artifactId>log4j</artifactId>

			<version>1.2.17</version>

		</dependency>

		<dependency>

			<groupId>dbunit</groupId>

			<artifactId>dbunit</artifactId>

			<version>2.2</version>

			<scope>test</scope>

		</dependency>

    <dependency>

		<groupId>commons-logging</groupId>

		<artifactId>commons-logging</artifactId>

		<version>1.1.1</version>

	</dependency>

		<dependency>

			<groupId>org.easymock</groupId>

			<artifactId>easymock</artifactId>

			<version>3.1</version>

			<scope>test</scope>

		</dependency>

			<dependency>

			<!-- ${project.xxx} 当前pom文件的任意节点的内容 -->

			<groupId>${project.groupId}</groupId>

			<artifactId>user-log</artifactId>

			<version>${project.version}</version>

			<!--  排除依赖

			<exclusions>

				<exclusion>

					<groupId>commons-logging</groupId>

					<artifactId>commons-logging</artifactId>

				</exclusion>

			</exclusions> -->

		</dependency>

		<dependency>

			<groupId>${project.groupId}</groupId>

			<artifactId>user-core</artifactId>

			<version>${project.version}</version>

		</dependency>

		</dependencies>

	</dependencyManagement>

</project>

maven 通过nexus创建工厂的配置的更多相关文章

07 Maven 使用Nexus创建私服
7. Maven 使用Nexus创建私服私服不是 Maven 的核心概念,它仅仅是一种衍生出来的特殊的 Maven 仓库.通过建立自己的私服,就可以降低中央仓库负荷.节省外网带宽.加速 Maven ...
大数据入门：Maven项目的创建及相关配置
目录 Maven项目的创建及相关配置一.Maven的介绍 1.Maven是什么: 2.Maven作用: 3.Maven项目的目录结构: 4.Maven的三点坐标: 5.maven的pom文件: 6. ...
[maven] 使用Nexus创建maven私有仓库
1.为什么需要maven私有仓库? 从Maven中央仓库下载所需的jar包,需要外网的支持.如果公司不能上外网的话则不能从中央仓库下载所需jar包,公司网速慢的时候也会影响项目构建的速度.用户可以用n ...
maven 之nexus仓库管理_私服配置
1.下载nexus私服下载地址:http://www.sonatype.org/downloads/nexus-latest.war 2.解压解压以下压缩包 3.配置环境变量 *\nexus-2. ...
【maven】之nexus常用的一些配置
nexus私服主要是在项目和maven中央仓库中间做代理,一般在公司内网或者公司内部的一些私包,都需要这么个产品.下面主要是关于maven和nexus之间的一些配置 1.在pom中配置nexus私服 ...
使用Nexus创建Maven私服
Nexus是一个强大的Maven仓库管理器,它极大地简化了自己内部仓库的维护和外部仓库的访问.利用Nexus你可以只在一个地方就能够完全控制访问和部署在你所维护仓库中的每个Artifact.Nexus ...
maven笔记（maven使用与安装，eclipse中maven的配置，maven项目的创建）
一.初识maven 1.maven是什么? 他是一个项目管理器,配置好pom配置文件后,maven会管理项目的依赖文件等,当项目用到外部jar包时,maven帮助我们去网上下载并打包发到Tomcat中 ...
Maven仓库Nexus的安装配置
1.下载nexus,最新版本是nexus-2.8.0-05 参考文章下载nexus-latest-bundle.zip文件后,并解压到 D:\nexus下配置nexus的环境变量:先配置NE ...
使用nexus创建maven私有仓库
nexus安装 nexus下载 wget https://sonatype-download.global.ssl.fastly.net/nexus/oss/nexus-2.11.1-01-bundl ...

随机推荐

MyBatis之传入参数——parameterType（转）
鸣谢:http://blog.csdn.net/liaoxiaohua1981/article/details/6862764 ------------------------------------ ...
[转载]C# HashTable 遍历与排序
private void Form1_Load(object sender, EventArgs e) { Hashtable ht = new Hashtable(); ht.Add("j ...
Firefly官方教程之Netconnect使用文档
1.distributed说明该模块包含了服务端与客户端通信的一些处理方法,包括发送数据的封装,协议头的封装,tcp通信时进行分包,处理粘包问题.2.结构解析 LiberateFactory,协议工厂 ...
Codeforces Round #239 (Div. 2) C. Triangle
time limit per test:1 secondmemory limit per test:256 megabytesinput:standard inputoutput:standard o ...
Cygwin环境编译/usr/include/sys/_types.h:72:20: 致命错误：stddef.h：can not found
环境介绍: win7_x64 +Cygwin64 gcc :4.8.2 g++:4.8.1 编译 c++的helloworld.cpp 一直失败! 代码如下: #include <iostrea ...
easyui源码翻译1.32--Calendar(日历)
前言前几天加班比较忙未能及时更新翻译的今天多发布几篇..下载该插件翻译源码日历控件显示一个月的日历,允许用户选择日期和移动到下一个或上一个月.默认情况下,一周的第一天是周日.它可以通过设置'f ...
Java程序发展之路
VC 为静态控件添加事件（修改ID号以后添加事件）
操作系统:Windows 7软件环境:Visual C++ 2008 SP1本次目的:为静态控件添加事件,如:STATIC.Picture Control等等有时候我们找到一个图片,为对话框背景添加 ...
ERP 及相关名词的含义
英文缩写英文名称中文含义 MRP Material requirements planning 物料需求计划 MRP II Manufacturing resource planning 制造 ...
Oracle EBS 预警系统管理
本章主要讲述配置和设置Oracle EBS预警系统管理, 它比较方便和及时发用户或系统对数据库操作情况.下面讲一操作步聚: 1.预警系统管理-->系统-->选项名称"Unix ...

maven 通过nexus创建工厂的配置

maven 通过nexus创建工厂的配置的更多相关文章

随机推荐

热门专题