[
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723211#action_12723211
]
Doug Cutting commented on ZOOKEEPER-224:
----------------------------------------
> why do we need ivy?
Ivy seems to be the best way to integrate Ant-based projects into the Maven
world. You write an Ivy config that lists the jars you depend on, and Ivy
fetches them, so that you no longer need to include them in svn. It can
generate a POM file from its configuration, so that applications that depend on
Zookeeper can easily get it and its dependencies. If you maintain your POM
file manually, then each time you add or upgrade a lib you have to update
multiple places, while with Ivy you only list your dependencies in one place.
I think Ivy can also push releases into Maven repos, but I haven't tried that
yet. I think this can also be done manually just by copying the .jar, .md5,
.sha1, .pom, and .asc files to the right directory on people.apache.org.
I did a simplisitic conversion of Avro to Ivy (AVRO-53,
http://svn.apache.org/viewvc?view=rev&revision=785776). The build.xml now
generates all of the files but the .asc. When I first try to do a release I'll
learn whether this works!
> 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.
