commented. Basically deploying the the maven repo is the same as deploying the final release artifact (it's just at a different directory on the same machine and has a different directory structure).
On Wed, Nov 19, 2008 at 1:02 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote: > Hi Hiram, I updated 224 with a few questions, if you could provide some > insight that would be helpful. > > Patrick > > Hiram Chirino wrote: >> >> I created issue: https://issues.apache.org/jira/browse/ZOOKEEPER-224 >> to track the request. >> >> Who's the current ZooKeeper release manager? >> >> On Fri, Nov 14, 2008 at 11:07 AM, Hiram Chirino <[EMAIL PROTECTED]> >> wrote: >>> >>> Hi Guys, >>> >>> I've create a small maven 2 repository for the ZooKeeper 3.0.0 release >>> at: >>> http://people.apache.org/~chirino/zk-repo/ >>> >>> Ideally the ZooKeeper PMC can review the artifacts validate that they >>> match the release, GPG sign all the poms and jars and push them out to >>> the main apache m2 maven repository so it can get synchronized into >>> the maven central repo. That's at >>> people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository >>> BTW. >>> >>> But For now maven users of ZooKeeper can add the following to their >>> build to automatically download the release: >>> >>> <repositories> >>> <repository> >>> <id>chirino-zk-repo</id> >>> <name>Private ZooKeeper Repo</name> >>> <url>http://people.apache.org/~chirino/zk-repo/</url> >>> </repository> >>> </repositories> >>> .... >>> <dependencies> >>> <dependency> >>> <groupId>org.apache.hadoop.zookeeper</groupId> >>> <artifactId>zookeeper</artifactId> >>> <version>3.0.0</version> >>> </dependency> >>> </dependencies> >>> >>> -- >>> Regards, >>> Hiram >>> >>> Blog: http://hiramchirino.com >>> >>> Open Source SOA >>> http://open.iona.com >>> >> >> >> > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
