[
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648686#action_12648686
]
Patrick Hunt commented on ZOOKEEPER-224:
----------------------------------------
Hiram, couple things:
1) is the "GPG project KEY" different from the key I normally use to sign the
release?
public release key here:
http://svn.apache.org/repos/asf/hadoop/zookeeper/dist/KEYS
2) how do I "deploy" it to the location you listed? What is that location?
3) do I need to name things in some particular way? What specific artifacts
have to be deployed?
4) what are the security implications? what keeps someone from signing a zk jar
with another key and deploying that?
Thanks!
> Deploy ZooKeeper 3.0.0 to a Maven Repository
> --------------------------------------------
>
> Key: ZOOKEEPER-224
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224
> Project: Zookeeper
> Issue Type: Task
> Components: build
> Affects Versions: 3.0.0
> Reporter: Hiram Chirino
> Assignee: Patrick Hunt
> Priority: Critical
>
> I've created the maven poms needed for the 3.0.0 release.
> The directory structure and artifacts located at:
> http://people.apache.org/~chirino/zk-repo/
> aka
> people.apache.org:/x1/users/chirino/public_html/zk-repo
> Just need sto get GPG signed by the project KEY and deployed to:
> people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository
> Who's the current ZooKeeper release manager?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.