上傳自己的構件(Jar)到Maven中央倉庫

背景：

用了Maven之後，你有沒有這樣的想法，自己一直在使用别人貢獻的代碼，自己能不能把自己覺得好的代碼也貢獻出來讓大家友善。

還有如果你也是一名程式員，你會不會覺得要是把自己積累起來日常常用的代碼工具元件放到Maven的中央倉庫之後，很友善維護和更新，

可以做到一次釋出，到處使用。

不用交給雲盤和代碼托管系統來管理，隻需要知道構件的坐标 + Maven之類的建構工具就能擷取想要的構件。

預備知識：

1.Java

http://www.oracle.com/technetwork/cn/java/javase/downloads/index.html

2.Maven

https://maven.apache.org/

3.Git

https://git-scm.com/

4. GnuGPG(gpg4win)

http://gpg4win.org/

5.Github

https://github.com/

6.Sonatype公司提供的

https://issues.sonatype.org

https://oss.sonatype.org

7.大概結構圖

準備工作：

1.JDK安裝配置

2 . Maven安裝配置

3 . Git安裝配置(可選)

4 . OpenGPG安裝配置

這四步完成之後的結果：

5.到 https://github.com/ 網站注冊一個賬号

6.到 https://issues.sonatype.org 網站注冊一個賬号

動手實驗：

(1) 在 https://github.com/ 網站建立一個倉庫

圖1-1：登陸

圖1-2：點選 “+” 好建立一個新的倉庫

圖1-3：倉庫的資訊填寫，這裡的必填項是倉庫的名稱Respository name

圖1-4：找到剛剛建立的倉庫，擷取倉庫的https連接配接位址和ssh連接配接位址

HTTPS位址：

https://github.com/zhangguangyong/codes.git

SSH位址：

[email protected]:zhangguangyong/codes.git

(2) 在 https://issues.sonatype.org 網站建立一個issues——建立的issues需要等待稽核

圖2-1：登陸

圖2-2：建立issues

圖2-3：Issues的資訊填寫

Description 和 Attachment 不需要填寫

點選Issues菜單，選擇剛剛建立Issues,等待管理者的審批

審批通過之後，會看到這樣的回複：

(3) 通過GnuGPG來建立一個公鑰

參考： http://my.oschina.net/huangyong/blog/226738

(4) 建立一個Maven項目 —— 配置 settings.xml、pom.xml、釋出到 https://oss.sonatype.org 倉庫

圖4-1：配置maven安裝目錄下 conf/settings.xml 檔案

settings.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: ${user.home}/.m2/repository <localRepository>/path/to/local/repo</localRepository> -->

<localRepository>D:/Dev/Repos/Maven</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. | -->

<!-- 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. | -->

<!-- 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. | -->

<!-- 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> -->

<username>zhanggy</username>

<password>xxxxxxxx</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.

| -->

<!-- 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> -->

</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.

| | -->

<!-- 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.

<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:

| | <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> -->

</ settings >

圖4-2：配置項目的pom.xml

項目的目錄結構(這裡是在eclipse中建立的,也可以自己手動建立)：

pom.xml 檔案的内容：

<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">

<groupId>com.github.zhangguangyong</groupId>

<artifactId>codes-common</artifactId>

<name>codes-common</name>

<url>https://github.com/zhangguangyong/codes</url>

<description>Code Reponsitory</description>

<name>The Apache Software License, Version 2.0</name>

<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>

</license>

</licenses>

<name>zhangguangyong</name>

<email>[email protected]</email>

</developer>

</developers>

<scm>

<connection>scm:[email protected]:zhangguangyong/codes.git</connection>

<developerConnection>scm:[email protected]:zhangguangyong/codes.git</developerConnection>

<url>https://github.com/zhangguangyong/codes</url>

</scm>

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

</properties>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

</dependency>

</dependencies>

<id>release</id>

<build>

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

<artifactId>maven-source-plugin</artifactId>

<phase>package</phase>

<goals>

</goals>

</execution>

</executions>

</plugin>

<artifactId>maven-javadoc-plugin</artifactId>

<artifactId>maven-gpg-plugin</artifactId>

<phase>verify</phase>

</plugins>

</build>

<url>https://oss.sonatype.org/content/repositories/snapshots/</url>

</snapshotRepository>

<url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>

</repository>

</distributionManagement>

</profile>

</project>

注意事項：settings.xml檔案節點< sever> 下的 <id> 節點需要與 pom.xml 檔案節點 <snapshotRepository> 和節點 <repository> 下的 <id> 節點保持一緻

圖4-3：釋出項目到 https://oss.sonatype.org 倉庫

使用指令cmd到項目的根路徑

執行指令：mvn clean deploy -P release

指令執行完之後，就可以到 https://oss.sonatype.org 下檢視自己剛剛釋出的構件了

(5) 到 https://oss.sonatype.org 倉庫操作自己釋出的構件(剛剛用maven釋出的)——1.關閉，2.釋出( 需要等到第(2)步的issues稽核通過才能釋出 )

圖5-1：進入 https://oss.sonatype.org 檢視自己釋出的構件

找到自己釋出的建構，點選關閉 ( 找組名是：com.github.xxx 開頭的，我們剛剛在pom.xml裡面填寫的元件就是 com.github.zhangguangyong)

關閉之後需要等待審批，審批成功之後，大概是這個樣子：

關閉的稽核通過之後，可進行釋出了（在釋出前需要確定之前建立Issues已經審批通過了，不然會報錯沒有權限）

這裡報錯的可能：

1. 剛剛建立的Issues還沒有審批通過

2. 項目的pom.xml裡面的< groupId > 與建立Issues時候填寫的 group Id 不一緻

(6) 在 https://oss.sonatype.org 釋出成功之後，再去 https://issues.sonatype.org 給管理者一個回報，說: "你的構件已經釋出成功了".

在 https://issues.sonatype.org 等待管理者的稽核，通過之後，就可以在 http://search.maven.org/ 上面所搜你釋出的構件了

圖6-1：通知Issues的管理者，你的構件在 https://oss.sonatype.org 上成功釋出

圖6-2：Issues管理者的回報如果是這樣的那恭喜你，你的構件就能夠在maven中央倉庫中搜尋到了： http://search.maven.org/

圖6-3：在 http://search.maven.org/ 上搜尋自己的構件

轉載自:https://my.oschina.net/u/2335754/blog/476676

參考：

http://my.oschina.net/huangyong/blog/226738

http://www.trinea.cn/dev-tools/upload-java-jar-or-android-aar-to-maven-center-repository