隨筆-50 評論-170 文章-0 trackbacks-0

Maven Artifacts如何部署到倉庫

順利

說明：該文檔只對有一定的Maven使用基礎的人有效，我也不會說的太具體，主要是一些配置和注意點。還有本文所用環境是Maven3，并不保證Maven2都能夠成功運行。不好意思，沒有太多時間來測試環境。

一、本地倉庫

使用 Nexus，如何搭建 Nexus 本文也就不說了。

pom.xml

<id>proj-releases</id>

<name>Proj Release Repository</name>

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

</repository>

<id>proj-snapshots</id>

<name>Proj Snapshots Repository</name>

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

</snapshotRepository>

</distributionManagement>

settings.xml

<id>proj-releases</id>

<username>admin</username>

<password>admin123</password>

</server>

<id>proj-snapshots</id>

<username>admin</username>

<password>admin123</password>

</server>

</servers>

二、Google Code 遠程倉庫

2.1 第一種方案使用wagon-webdav來遠程上傳repo

參考：http://marshal.easymorse.com/archives/2644

pom.xml

<id>usc-google-code-repo</id>

<name>Google Code Repo for USC (releases)</name>

<url>dav:https://usc.googlecode.com/svn/maven-repo/releases</url>

<uniqueVersion>false</uniqueVersion>

</repository>

<id>usc-google-code-snapshot</id>

<name>Google Code Repo USC (snapshots)</name>

<url>dav:https://usc.googlecode.com/svn/maven-repo/snapshots</url>

<uniqueVersion>false</uniqueVersion>

</snapshotRepository>

</distributionManagement>

<build>

<groupId>org.apache.maven.wagon</groupId>

<artifactId>wagon-webdav</artifactId>

</extension>

</extensions>

</build>

settings.xml

<id>usc-google-code-repo</id>

<username>your google email</username>

<password>your google code project password</password>

</server>

<id>usc-google-code-snapshot</id>

<username>your google email</username>

<password>your google code project password</password>

</server>

</servers>

注意點

1.repo url 是 dav: ...

2.其他project or module 依賴使用的時候，請加上 repositories 和 group id..

e.g.

<id>usc-google-code-repo</id>

<name>Google Code Repo for USC (releases)</name>

<url>https://usc.googlecode.com/svn/maven-repo/releases</url>

</repository>

</repositories>

2.2 第二種方案使用wagon-svn來遠程上傳repo

參考：http://www.dev-articles.com/article/Google-Code-personal-maven-repository-30001

pom.xml

<id>usc-google-code-repo</id>

<name>Google Code Repo for USC (releases)</name>

<url>svn:https://usc.googlecode.com/svn/maven-repo/releases</url>

<uniqueVersion>false</uniqueVersion>

</repository>

<id>usc-google-code-snapshot</id>

<name>Google Code Repo USC (snapshots)</name>

<url>svn:https://usc.googlecode.com/svn/maven-repo/snapshots</url>

<uniqueVersion>false</uniqueVersion>

</snapshotRepository>

</distributionManagement>

<build>

<groupId>org.jvnet.wagon-svn</groupId>

<artifactId>wagon-svn</artifactId>

</extension>

</extensions>

</build>

settings.xml

<id>usc-google-code-repo</id>

<username>your google email</username>

<password>your google code project password</password>

</server>

<id>usc-google-code-snapshot</id>

<username>your google email</username>

<password>your google code project password</password>

</server>

</servers>

注意點

1.repo url 是 svn: ...
2.其他project or module 依賴使用的時候，請加上 repositories 和 group id..

e.g.

<id>usc-google-code-repo</id>

<name>Google Code Repo for USC (releases)</name>

<url>https://usc.googlecode.com/svn/maven-repo/releases</url>

</repository>

</repositories>

3.好像有個權限認證的問題，會有選擇，選擇最后一項 p: (p)ermanently（永久）應該是ok的.

信息差不多如下:

Uploading: svn:https://usc.googlecode.com/svn/maven-repo/releases/org/usc/file/filename-batch-converter/app-parent/3.0.5/app-parent-3.0.5.pom
Error validating server certificate for 'https://usc.googlecode.com:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
- The certificate hostname does not match.
Certificate information:
- Subject: CN=*.googlecode.com, O=Google Inc, L=Mountain View, ST=California, C=US
- Valid: from Fri Aug 12 11:49:18 CST 2011 until Sun Aug 12 11:59:18 CST 2012
- Issuer: CN=Google Internet Authority, O=Google Inc, C=US
- Fingerprint: 28:92:6b:9b:40:10:cc:0e:4c:16:a4:78:7f:bb:1a:8d:d4:d1:d3:27
(R)eject, accept (t)emporarily or accept (p)ermanently?

個人感覺使用wagon-svn沒有使用wagon-webdav deploy 快，可能是使用協議的問題。

2.3 第三種方案（這才是遠程）

上面的兩種方法，都必須要配置 repository，如果是普通用戶，并不會關注到這些倉庫配置，當他們不配置這些倉庫URL的，又想使用你的Jar，可否？能否直接使用 group id + artifactId + version 就能依賴到了，答案是肯定的。使用 OSS Sonatype一個代理 Repository，過一段時間會更新到Maven Central Repo。