james strachan commented on ZOOKEEPER-83:

So long as dependencies don't change much and the build process doesn't undergo 
any major radical changes, its not gonna require much in the way of maintenance 
keeping the maven build going. (BTW Maven can auto-generate an Ant build too 
which uses the Maven ant tasks to work with dependencies and repos). Am sure 
Hiram or myself would happily keep the maven build ticking along. So its zero 
overhead to the ZK team.

In terms of Ivy; yeah I've heard it can work with maven repos; but I've never 
worked on a project that really uses it - it just seams much easier if you 
wanna work with maven metadata, dependencies, hierarchical projects and 
repositories to just use Maven :). There's a zillion issues with keeping your 
metadata up to date on compile/optional/test dependencies and dealing with 
hierarchial projects and transitive dependency issues - so I've no idea what 
issues you'd run into using Ivy - over the years we've bumped into a zillion 
issues with Maven :( so I certainly understand the maven resistence. Everyone 
has a love/hate relationship with it - until you try to re-implement what it 
does in Ant and you end up with some kinda grudging respect for it :). 
(Especially if you ever have to do any OSGi work!)

But sure if you guys wanna figure out the Ivy route so it'd be easy to build, 
test and install the ZK jars into a local or remote Maven repo, I'd be really 
happy! Given both Hiram and myself have been really heavy Maven users for many 
years (after being heavy Ant users before then) I doubt you'll be getting any 
Ant+Ivy patches for the build system from either of us though :).

Heck if the Maven build only lives around until someone figures out how to 
replace it with Ant+Ivy I think we'd all be happy; so starting with a maven 
build then replacing it later if someone can figure out how to do it with 
Ant+Ivy sounds a reasonable approach. (And we could always keep the maven build 
ticking along until the Ant+Ivy approach really does work).

> Switch to using maven to build ZooKeeper
> ----------------------------------------
>                 Key: ZOOKEEPER-83
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-83
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: build
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>         Attachments: zookeeper-mavened.tgz
> Maven is a great too for building java projects at the ASF.  It helps 
> standardize the build a bit since it's a convention oriented.
> It's dependency auto downloading would remove the need to store the 
> dependencies in svn, and it will handle many of the suggested ASF policies 
> like gpg signing of the releases and such.
> The ZooKeeper build is almost vanilla except for the jute compiler bits.  
> Things that would need to change are:
>  * re-organize the source tree a little so that it uses the maven directory 
> conventions
>  * seperate the jute bits out into seperate modules so that a maven plugin 
> can be with it

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