How to deploy internal artifact » History » Version 4
chin-yeh, 04/22/2011 02:36 PM
1 | 1 | chin-yeh | h1. How to deploy internal artifact |
---|---|---|---|
2 | |||
3 | Before the deployment, you may need to check out the existing artifact in the Nexus, [[SearchBrowse_artifact|Search/Browsse Artifact]]. |
||
4 | |||
5 | # To deploy artifact to internal repositories, append the following to your project's POM (see also "Maven Deploy Plugin":http://maven.apache.org/plugins/maven-deploy-plugin/usage.html) : |
||
6 | <pre> |
||
7 | <repository> |
||
8 | <uniqueVersion>false</uniqueVersion> |
||
9 | <id>releases</id> |
||
10 | <url>http://192.168.2.13:8081/nexus/content/repositories/releases</url> |
||
11 | </repository> |
||
12 | <snapshotRepository> |
||
13 | <uniqueVersion>true</uniqueVersion> |
||
14 | <id>snapshots</id> |
||
15 | <url>http://192.168.2.13:8081/nexus/content/repositories/snapshots</url> |
||
16 | </snapshotRepository> |
||
17 | </pre> |
||
18 | 4 | chin-yeh | ** for connector project, all projects inherit the above similiar settings from a parent POM, *ecosway-parent*. Therefore, you just need to update the parent POM and all its inherited projects will get the latest changes. |
19 | 1 | chin-yeh | # <code>cd</code> to your project folder, and execute the maven goal, *deploy*: |
20 | <pre> |
||
21 | mvn deploy |
||
22 | </pre> |
||
23 | 3 | chin-yeh | # if success, checkout the deployed artifact in "Nexus":http://192.168.2.13:8081/nexus/index.html#welcome |
24 | 2 | chin-yeh | # done. |