[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository

2009-04-14 Thread Todd Greenwood-Geer (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12698871#action_12698871
 ] 

Todd Greenwood-Geer commented on ZOOKEEPER-224:
---

https://issues.apache.org/jira/browse/HADOOP-3305

The hadoop issue(HADOOP-3305) has been resolved, and it appears that 
hadoop-core has been deployed to maven. Is there any possibility of deploying 
zookeeper to maven?





 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.



[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository

2008-11-26 Thread Patrick Hunt (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12651081#action_12651081
 ] 

Patrick Hunt commented on ZOOKEEPER-224:


Thanks for the feedback Doug, I hadn't thought of that but it makes sense.

I definitely think we should support this, but it's quickly turning from extra 
work for me, to a lot of extra work. ;-)

I talked with Nigel who's the release manager for Hadoop Core. There is recent 
progress on 
https://issues.apache.org/jira/browse/HADOOP-3305 which is very similar to this 
issue.

Nigel mentioned that we should be able to get some time from the contributors 
to core's build management. We currently use the hadoop core build/release 
process, it's a huge benefit to me not to have to reinvent the wheel and just 
use their vetted processes. I'll talk with Nigel to see what can be done wrt 
getting the work from 3305 ported into ZK build/release process. I'm going to 
hold off on any changes related to this issue (build or release) until 3305 
settles, worst case we can port the work from 3305 ourselves.



 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.



[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository

2008-11-25 Thread Doug Cutting (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650636#action_12650636
 ] 

Doug Cutting commented on ZOOKEEPER-224:


Shouldn't the pom  metadata files be either included in svn or generated by 
the build?  We shouldn't be publishing artifacts without a documented process 
in place so that any committer can build the next release.  So the creation of 
this needs to be part of http://wiki.apache.org/hadoop/ZooKeeper/HowToRelease.  
We shouldn't generate new release artifacts after the release vote.  Maybe, if 
the process is documented, and Pat's willing to create  publish these 
artifacts after the fact, an exception can be made for a few past releases, but 
going forward, this is not a good process.

 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.



[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository

2008-11-24 Thread Hiram Chirino (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650272#action_12650272
 ] 

Hiram Chirino commented on ZOOKEEPER-224:
-

Q: How are the .sha1 files generated? What's the command?
A: 
{code}
prompt openssl dgst -md5  inputfile
prompt openssl dgst -sha1  inputfile
{code}

Q: I update maven-metadata.xml and regenerate the md5/sha1?
A: yes. maven-metadata.xml is mainly used by the plugin download system maven 
has. it will consult this file to see what the latest version of the artifact 
is.  So while it's not critical that the metadata is maintained, it is done for 
all maven deployed artifacts so ideally it should be done.

Q: And also create a new 3.0.1 subdir at the same level as the 3.0.0 subdir?
A: Yes

Q: Should I include 3.0.0 as well or just 3.0.1?
A: Yes please.  That way all your releases are available via Maven.

 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.



[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository

2008-11-19 Thread Hiram Chirino (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649119#action_12649119
 ] 

Hiram Chirino commented on ZOOKEEPER-224:
-

Hi Patrick,

1) Yeah.. same key used to sign the distro.  Just so that folks who get the 
artifacts from maven can verify that it's from a trusted source.

2) The /www/people.apache.org/repo/m2-ibiblio-rsync-repository directory is the 
Apache Maven2 release repository.  Only official releases should be pushed 
there.  Artifacts deployed here will get mirrored to the maven central 
repository.  You deploy to this the same way you deployed the release distro to 
people.apache.org:/www/www.apache.org/dist/hadoop/zookeeper.  I would just scp 
to people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository

3) Yes. The entire directory structure and files contained within the 
http://people.apache.org/~chirino/zk-repo/ directory need to be preserved.  If 
my directory had GPG signed all the artifacts (including poms), you would have 
been able to ssh into the people.apache.org machine and run: 
{code}
cp -r /x1/users/chirino/public_html/zk-repo/* 
/www/people.apache.org/repo/m2-ibiblio-rsync-repository
{code}

4) Same implications that you have when your deploy your release distro to the 
people.apache.org:/www/www.apache.org/dist/hadoop/zookeeper directory.  As long 
as the people.apache.org does not get hacked only Apache committers can deploy 
a signed zk jar.  Just like with release distros, the onus of verifying jar 
signatures lies with the downstream user.  You guys should document this well 
on your website along with the KEYS file they should validate against.  And 
hope that the website hosting the KEYS file does not get hacked too :)  (The 
chain of trust and security is so fragile!)






 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.



[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository

2008-11-18 Thread Patrick Hunt (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.



[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository

2008-11-17 Thread Patrick Hunt (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648447#action_12648447
 ] 

Patrick Hunt commented on ZOOKEEPER-224:


Hey there, I'm the current release manager (phunt).


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