1. maven setting配置

  1. <?xml version="1.0" encoding="UTF-8"?>
  2.  
  3. <!--
  4. Licensed to the Apache Software Foundation (ASF) under one
  5. or more contributor license agreements. See the NOTICE file
  6. distributed with this work for additional information
  7. regarding copyright ownership. The ASF licenses this file
  8. to you under the Apache License, Version 2.0 (the
  9. "License"); you may not use this file except in compliance
  10. with the License. You may obtain a copy of the License at
  11.  
  12. http://www.apache.org/licenses/LICENSE-2.0
  13.  
  14. Unless required by applicable law or agreed to in writing,
  15. software distributed under the License is distributed on an
  16. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  17. KIND, either express or implied. See the License for the
  18. specific language governing permissions and limitations
  19. under the License.
  20. -->
  21.  
  22. <!--
  23. | This is the configuration file for Maven. It can be specified at two levels:
  24. |
  25. | 1. User Level. This settings.xml file provides configuration for a single user,
  26. | and is normally provided in ${user.home}/.m2/settings.xml.
  27. |
  28. | NOTE: This location can be overridden with the CLI option:
  29. |
  30. | -s /path/to/user/settings.xml
  31. |
  32. | 2. Global Level. This settings.xml file provides configuration for all Maven
  33. | users on a machine (assuming they're all using the same Maven
  34. | installation). It's normally provided in
  35. | ${maven.conf}/settings.xml.
  36. |
  37. | NOTE: This location can be overridden with the CLI option:
  38. |
  39. | -gs /path/to/global/settings.xml
  40. |
  41. | The sections in this sample file are intended to give you a running start at
  42. | getting the most out of your Maven installation. Where appropriate, the default
  43. | values (values used when the setting is not specified) are provided.
  44. |
  45. |-->
  46. <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  47. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  48. xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  49. <!-- localRepository
  50. | The path to the local repository maven will use to store artifacts.
  51. |
  52. | Default: ${user.home}/.m2/repository
  53.  
  54. -->
  55. <localRepository>E:\DevelopEnvironment\Maven\repository</localRepository>
  56. <!-- interactiveMode
  57. | This will determine whether maven prompts you when it needs input. If set to false,
  58. | maven will use a sensible default value, perhaps based on some other setting, for
  59. | the parameter in question.
  60. |
  61. | Default: true
  62. <interactiveMode>true</interactiveMode>
  63. -->
  64.  
  65. <!-- offline
  66. | Determines whether maven should attempt to connect to the network when executing a build.
  67. | This will have an effect on artifact downloads, artifact deployment, and others.
  68. |
  69. | Default: false
  70. <offline>false</offline>
  71. -->
  72.  
  73. <!-- pluginGroups
  74. | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
  75. | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
  76. | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
  77. |-->
  78. <pluginGroups>
  79. <!-- pluginGroup
  80. | Specifies a further group identifier to use for plugin lookup.
  81. <pluginGroup>com.your.plugins</pluginGroup>
  82. -->
  83. </pluginGroups>
  84.  
  85. <!-- proxies
  86. | This is a list of proxies which can be used on this machine to connect to the network.
  87. | Unless otherwise specified (by system property or command-line switch), the first proxy
  88. | specification in this list marked as active will be used.
  89. |-->
  90. <proxies>
  91. <!-- proxy
  92. | Specification for one proxy, to be used in connecting to the network.
  93. |
  94. <proxy>
  95. <id>optional</id>
  96. <active>true</active>
  97. <protocol>http</protocol>
  98. <username>proxyuser</username>
  99. <password>proxypass</password>
  100. <host>proxy.host.net</host>
  101. <port>80</port>
  102. <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  103. </proxy>
  104. -->
  105. </proxies>
  106.  
  107. <!-- servers
  108. | This is a list of authentication profiles, keyed by the server-id used within the system.
  109. | Authentication profiles can be used whenever maven must make a connection to a remote server.
  110. |-->
  111. <servers>
  112. <!-- server
  113. | Specifies the authentication information to use when connecting to a particular server, identified by
  114. | a unique name within the system (referred to by the 'id' attribute below).
  115. |
  116. | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
  117. | used together.
  118. |
  119. <server>
  120. <id>deploymentRepo</id>
  121. <username>repouser</username>
  122. <password>repopwd</password>
  123. </server>
  124. -->
  125.  
  126. <!-- Another sample, using keys to authenticate.
  127. <server>
  128. <id>siteServer</id>
  129. <privateKey>/path/to/private/key</privateKey>
  130. <passphrase>optional; leave empty if not used.</passphrase>
  131. </server>
  132. -->
  133. <server>
  134. <id>releases</id>
  135. <username>admin</username>
  136. <password>admin123</password>
  137. </server>
  138. <server>
  139. <id>snapshots</id>
  140. <username>admin</username>
  141. <password>admin123</password>
  142. </server>
  143. </servers>
  144.  
  145. <!-- mirrors
  146. | This is a list of mirrors to be used in downloading artifacts from remote repositories.
  147. |
  148. | It works like this: a POM may declare a repository to use in resolving certain artifacts.
  149. | However, this repository may have problems with heavy traffic at times, so people have mirrored
  150. | it to several places.
  151. |
  152. | That repository definition will have a unique id, so we can create a mirror reference for that
  153. | repository, to be used as an alternate download site. The mirror site will be the preferred
  154. | server for that repository.
  155. |-->
  156. <mirrors>
  157. <!-- mirror
  158. | Specifies a repository mirror site to use instead of a given repository. The repository that
  159. | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
  160. | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
  161. |
  162. <mirror>
  163. <id>mirrorId</id>
  164. <mirrorOf>repositoryId</mirrorOf>
  165. <name>Human Readable Name for this Mirror.</name>
  166. <url>http://my.repository.com/repo/path</url>
  167. </mirror>
  168. -->
  169. <mirror>
  170. <id>nexus-releases</id>
  171. <mirrorOf>*</mirrorOf>
  172. <url>http://localhost:8081/nexus/content/groups/public</url>
  173. </mirror>
  174. <mirror>
  175. <id>nexus-snapshots</id>
  176. <mirrorOf>*</mirrorOf>
  177. <url>http://localhost:8081/nexus/content/repositories/snapshots/</url>
  178. </mirror>
  179. </mirrors>
  180.  
  181. <!-- profiles
  182. | This is a list of profiles which can be activated in a variety of ways, and which can modify
  183. | the build process. Profiles provided in the settings.xml are intended to provide local machine-
  184. | specific paths and repository locations which allow the build to work in the local environment.
  185. |
  186. | For example, if you have an integration testing plugin - like cactus - that needs to know where
  187. | your Tomcat instance is installed, you can provide a variable here such that the variable is
  188. | dereferenced during the build process to configure the cactus plugin.
  189. |
  190. | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
  191. | section of this document (settings.xml) - will be discussed later. Another way essentially
  192. | relies on the detection of a system property, either matching a particular value for the property,
  193. | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
  194. | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
  195. | Finally, the list of active profiles can be specified directly from the command line.
  196. |
  197. | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
  198. | repositories, plugin repositories, and free-form properties to be used as configuration
  199. | variables for plugins in the POM.
  200. |
  201. |-->
  202. <profiles>
  203. <!-- profile
  204. | Specifies a set of introductions to the build process, to be activated using one or more of the
  205. | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
  206. | or the command line, profiles have to have an ID that is unique.
  207. |
  208. | An encouraged best practice for profile identification is to use a consistent naming convention
  209. | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
  210. | This will make it more intuitive to understand what the set of introduced profiles is attempting
  211. | to accomplish, particularly when you only have a list of profile id's for debug.
  212. |
  213. | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
  214. <profile>
  215. <id>jdk-1.4</id>
  216.  
  217. <activation>
  218. <jdk>1.4</jdk>
  219. </activation>
  220.  
  221. <repositories>
  222. <repository>
  223. <id>jdk14</id>
  224. <name>Repository for JDK 1.4 builds</name>
  225. <url>http://www.myhost.com/maven/jdk14</url>
  226. <layout>default</layout>
  227. <snapshotPolicy>always</snapshotPolicy>
  228. </repository>
  229. </repositories>
  230. </profile>
  231. -->
  232. <profile>
  233. <id>jdk-1.8</id>
  234. <activation>
  235. <activeByDefault>true</activeByDefault>
  236. <jdk>1.8</jdk>
  237. </activation>
  238. <properties>
  239. <maven.compiler.source>1.8</maven.compiler.source>
  240. <maven.compiler.target>1.8</maven.compiler.target>
  241. <maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
  242. </properties>
  243. </profile>
  244. <profile>
  245. <id>nexusTest</id>
  246. <repositories>
  247. <repository>
  248. <id>local-nexus</id>
  249. <url>http://localhost:8081/nexus/content/groups/public/</url>
  250. <releases>
  251. <enabled>true</enabled>
  252. </releases>
  253. <snapshots>
  254. <enabled>true</enabled>
  255. </snapshots>
  256. </repository>
  257. </repositories>
  258. </profile>
  259.  
  260. <!--
  261. | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
  262. | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
  263. | might hypothetically look like:
  264. |
  265. | ...
  266. | <plugin>
  267. | <groupId>org.myco.myplugins</groupId>
  268. | <artifactId>myplugin</artifactId>
  269. |
  270. | <configuration>
  271. | <tomcatLocation>${tomcatPath}</tomcatLocation>
  272. | </configuration>
  273. | </plugin>
  274. | ...
  275. |
  276. | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
  277. | anything, you could just leave off the <value/> inside the activation-property.
  278. |
  279. <profile>
  280. <id>env-dev</id>
  281.  
  282. <activation>
  283. <property>
  284. <name>target-env</name>
  285. <value>dev</value>
  286. </property>
  287. </activation>
  288.  
  289. <properties>
  290. <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  291. </properties>
  292. </profile>
  293. -->
  294. </profiles>
  295.  
  296. <!-- activeProfiles
  297. | List of profiles that are active for all builds.
  298. |
  299. <activeProfiles>
  300. <activeProfile>alwaysActiveProfile</activeProfile>
  301. <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  302. </activeProfiles>
  303. -->
  304. <!-- 激活id为 nexusTest 的profiles -->
  305. <activeProfiles>
  306. <activeProfile>nexusTest</activeProfile>
  307. </activeProfiles>
  308. </settings>

2. 项目pom文件配置

  1. <?xml version="1.0" encoding="UTF-8"?>
  2.  
  3. <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  4. xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  5. <modelVersion>4.0.0</modelVersion>
  6.  
  7. <groupId>com.zyu</groupId>
  8. <artifactId>test</artifactId>
  9. <version>1.0-SNAPSHOT</version>
  10.  
  11. <!-- 配置私服 -->
  12. <distributionManagement>
  13. <repository>
  14. <id>releases</id>
  15. <url>http://localhost:8081/nexus/content/repositories/releases</url>
  16. </repository>
  17. <snapshotRepository>
  18. <id>snapshots</id>
  19. <url>http://localhost:8081/nexus/content/repositories/snapshots</url>
  20. </snapshotRepository>
  21. </distributionManagement>
  22.  
  23. <dependencies>
  24.  
  25. <!-- https://mvnrepository.com/artifact/org.springframework/spring-core -->
  26. <dependency>
  27. <groupId>org.springframework</groupId>
  28. <artifactId>spring-core</artifactId>
  29. <version>5.2.0.RELEASE</version>
  30. </dependency>
  31.  
  32. </dependencies>
  33.  
  34. </project>

3. 打包上传

上传成功~

Nexus 上传项目到私服的更多相关文章

  1. window下玩转maven私服全流程,融合创建仓库、上传项目资源、下载私服资源

    ​ 在互联网项目开发浪潮中,maven成为了项目管理依赖的重要工具,更多时候maven只作为拉取外部依赖的手段.但出于安全的考虑的,部门企业难免封装一些私有的工具类,或开源框架的二次开发封装,mave ...

  2. git上传项目代码到github

    参考: git学习——上传项目代码到github github上传时出现error: src refspec master does not match any解决办法 git 上传本地文件到gith ...

  3. GitHub教程--上传项目四步法 GitBash命令行下使用方法

    之前就用过GitHub,感觉用GitHub托管自己的代码非常不错.可是之前用的都是窗口化的TortoiseGit,省了很多命令行的操作,但是个人非常喜欢使用命令行,于是,今天就试着用了用GitBash ...

  4. svn用Cornerstone上传项目丢失静态库.a问题的解决

    最近电脑重装系统后,装上Cornerstone上传项目后,发现又有丢失.a文件的问题,这里说一下解决办法,打开Preferences-->Subversion-->General,将Use ...

  5. 在Eclipse里面使用git上传项目到码云

    Eclispe上使用git 1.安装git 按照下图的步骤: 安装过就不用再安装了,没有安装的安装一下! 安装完毕之后:需要做一些初始化的设置: 2.上传项目到码云上 1.首先在码云上建立一个项目 2 ...

  6. IDEA上传项目至git

    今天来分享一下从idea上传项目至coding的过程. 本文基于windows系统. idea提供了很方便的控制git的界面化操作,除了安装git和一些必要的配置之外,用到命令行的地方会非常少. 1: ...

  7. Android快速实现上传项目到Github

    本文为skylinelin原创,转载请注明出处! 一.简介 现在在网上浏览关于Git的文章,基本上都是使用命令行(Git Bash),命令行效率是很高的,但是有一定的复杂性,现在我们看如何用AS来讲项 ...

  8. MyEclipse2015上传项目到GitHub(很详细)

    MyEclipse 2015 默认已经安装了git插件,在MyEclipse中上传项目到github的步骤如下: 1.github官网(https://github.com)申请开通账号(略) 1.1 ...

  9. SVN上传项目步骤

    1.svn上传项目  首先选中父工程 ,右键选中Team的share project 2.share完再选中SVN 3.选中项目  一个一个share project 4.

随机推荐

  1. Java 文章链接

    Java表单验证封装类 https://www.cnblogs.com/linjiqin/archive/2013/11/18/3429424.html 微信企业号接入JDK6和JDK7及JDK8加解 ...

  2. Java初中级面试笔记及对应视频讲解

    笔试题链接:点击打开链接   密码:提取码:7h9e 视频下载链接: 点击打开链接  提取码:hyye 百万it课程 https://pan.baidu.com/s/1ldJ_Ak7y0VL5Xmy9 ...

  3. mysql初识笔记

    一.初始mysql mysql介绍: mysql版本: 版本号=3个数字+1个后缀 mysql-5.0.9-beta 5 0 9 Beta 主版本号 发行级别 发行稳定级别 发行系列 发行系列的版本号 ...

  4. C语言复习————基本数据类型、运算符和表达式

    数据类型/运算符/表达式 主要分两部分介绍,第一部分介绍常用的数据类型,例如:常量和变量/整型/实型/字符型:第二部分介绍算数运算符和算数表达式以及赋值运算符和逗号运算符. 一. 常用的数据类型 1. ...

  5. Scala 多继承问题

    多继承问题: object LoadIssueDemo extends App { import java.io.PrintWriter trait Logger { def log(msg: Str ...

  6. Spring Boot 2.X(四):Spring Boot 自定义 Web MVC 配置

    0.准备 Spring Boot 不仅提供了相当简单使用的自动配置功能,而且开放了非常自由灵活的配置类.Spring MVC 为我们提供了 WebMvcConfigurationSupport 类和一 ...

  7. ADB命令无法导出文件到物理机上处理办法

    因为想查看一下脚本生成的sqlite文件.就想导出文件,,结果导出adb pull命令一直报错.使用su也是错误的..最后发现adb pull 不能再adb的命令状态下执行.需要退出adb命令.然后直 ...

  8. Java基础学习(八) - 多线程

    理解线程 进程是指一个内存中运行的应用程序,系统运行一个程序即是一个进程从创建,运行,结束的过程. 线程是进程中的一个执行单元,负责当前进程中程序的执行,一个进程中至少有一个线程. 多线程的特点是并发 ...

  9. js对数组、对象的深拷贝、复制

    基本类型的数据是存放在栈内存中的,而引用类型的数据是存放在堆内存中的 基本类型:Number Boolean undefined String Null 引用类型:Object Function js ...

  10. Docker的安装及加速器配置

    简介 Docker是一个开源项目 ,其主要目标是实现轻量级的操作系统虚拟化解决方案.Docker的基础是Linux容器(LXC)等技术.在LXC的基础上Docker进行了进一步的封装,让用户不需关心容 ...