Patrick Hunt commented on ZOOKEEPER-224:

Hi Paolo, thanks for taking a look at this! 

See ZOOKEEPER-537 for background. 

Support for maven repo was contributed by Thomas & Hiram, I have limited/no 
experience with this to provide good answers to your questions. We've gotten a 
number of requests for Maven support, but not much help. We have limited maven 
experience so there may be some issues to shake out.

Until the release has been approved by the PMC we only publish the release 
candidate archive. It includes the generated pom and jars destined for maven 
deployment. That's not sufficient to test?

create-cppunit-configure is the c part of the build, it requires libraries such 
as cppunit to be installed. You might be able to get around this by using "ant 
compile-test" or "ant test-core-java" to compile/test the java code 

I don't know about maven naming conventions, is there a pointer to docs on 
whether to use sources vs src?

> 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:
> 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