Paolo Castagna commented on ZOOKEEPER-224:
Where can I find the latest ZooKeeper release candidate?
The only Ant target which generates the pom.xml file is "package". I have
removed the dependency on "create-cppunit-configure" just to see the pom.xml
file generated by Ivy.
The pom.xml file generated by Ivy seems fine. The only problem I foresee is
related to log4j, but everybody has that.
Ideally, you would like to have something like this in your pom.xml, however I
do not know how to tell Ivy to generate this:
A similar issue has been discussed here:
About sources vs. src:
"If you are not using Maven as your build system, and want something uploaded
to the Central Repository then you just need to make a bundle jar manually.
Please use the jar executable, not zip, pkzip or equivalent. The bundle
should have the following content:
foo-1.0.jar (or whatever artifact is referred to in the pom.xml)
The names of the jar files inside the bundle must be built from the
<artifactId> and <version> in the pom.xml file, like this:
> Deploy ZooKeeper jars/artifacts 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.3.0
> I've created the maven poms needed for the 3.0.0 release.
> The directory structure and artifacts located at:
> Just need sto get GPG signed by the project KEY and deployed to:
> 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.