Hiram Chirino commented on ZOOKEEPER-224:

Q: How are the .sha1 files generated? What's the command?
prompt> openssl dgst -md5 < inputfile
prompt> openssl dgst -sha1 < inputfile

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.

Reply via email to