You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Benjamin Reed (JIRA)" <ji...@apache.org> on 2009/06/19 00:52:07 UTC

[jira] Updated: (ZOOKEEPER-224) Deploy ZooKeeper 3.2.0 to a Maven Repository

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Reed updated ZOOKEEPER-224:
------------------------------------

    Fix Version/s: 3.2.0
          Summary: Deploy ZooKeeper 3.2.0 to a Maven Repository  (was: Deploy ZooKeeper 3.0.0 to a Maven Repository)

In the next release can we get zookeeper.jar zookeeper-test.jar and bookeeper.jar published to maven? is there some simple procedure to apply to our built jar files to make them deployable?

> Deploy ZooKeeper 3.2.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
>             Fix For: 3.2.0
>
>
> 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.