[
https://issues.apache.org/jira/browse/ZOOKEEPER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated ZOOKEEPER-1430:
------------------------------------------
Attachment: ZOOKEEPER-1430-V3.patch
this v3 patch user gpg profile to get the gpg.passphrase for signing the
artifact when uploading to staging.
Details below:
ant mvn-deploy
- this deploys the snapshot artifact to the nexus snapshot repository
- expects jar files has -SNAPSHOT suffix present in it.
ant mvn-deploy -Dstaging=true
- Essentially this is done when an Release Candidate is pushed.
- This target deploy's release versioned artifact to the nexus staging
profile
- For staging the artifacts, staging repo requires the artifacts be signed
using gpg keys.
- To sign the artifact using gpg keys , one has to provide the gpg
passphrase in plain text in the ~/.m2/settings.xml
If one is worried about leaving plain text password, they can refer to
http://maven.apache.org/guides/mini/guide-encryption.html for encrypting the
passphrase.
Here is the ~/.m2/settings.xml that I used for testing the targets above.
{code:xml}
<settings>
<servers>
<server>
<id>apache.snapshots.https</id>
<username>XXXXXXX</username>
<password>XXXXXXXX</password>
</server>
<server>
<id>apache.staging.https</id>
<username>XXXXXXX</username>
<password>XXXXXXX</password>
</server>
</servers>
<profiles>
<profile>
<id>gpg</id>
<properties>
<gpg.passphrase>XXXXXXX</gpg.passphrase>
</properties>
</profile>
</profiles>
</settings>
{code}
> add maven deploy support to the build
> -------------------------------------
>
> Key: ZOOKEEPER-1430
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1430
> Project: ZooKeeper
> Issue Type: Task
> Components: build
> Affects Versions: 3.4.4, 3.5.0
> Reporter: Patrick Hunt
> Assignee: Giridharan Kesavan
> Priority: Blocker
> Fix For: 3.4.6, 3.5.0
>
> Attachments: ZOOKEEPER-1430-3.4.patch, ZOOKEEPER-1430.patch,
> ZOOKEEPER-1430.patch, ZOOKEEPER-1430-V1.PATCH, ZOOKEEPER-1430-V2.PATCH,
> ZOOKEEPER-1430-V3.patch
>
>
> Infra is phasing out the current mechanism we use to deploy maven artifacts.
> We need to move to repository.apache.org (nexus).
> In particular we need to ensure the following artifacts get published:
> * zookeeper-3.x.y.jar
> * zookeeper-3.x.y-sources.jar
> * zookeeper-3.x.y-tests.jar
> * zookeeper-3.x.y-javadoc.jar
> In 3.4.4/3.4.5 we missed the tests jar which caused headaches for downstream
> users, such as Hadoop.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
