[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616200#action_12616200
 ] 

chirino edited comment on ZOOKEEPER-83 at 7/23/08 11:18 AM:
------------------------------------------------------------------

Hi folks.. 

To make the maven re-org super simple to apply I created a temp private branch 
so that the changes can easily be merged into trunk.
This branch also has an updated ant build which works with the new maven 
directory structure.

To merge the changes back into trunk, just run the follow in a clean trunk 
checkout:

{code}
svn merge -r 679094:679134 
https://svn.apache.org/repos/asf/activemq/sandbox/zookeeper
{code}

      was (Author: chirino):
    Hi folks.. 

To make the maven re-org super simple to apply I created a temp private branch 
so that the changes can easily be merged into trunk.
This branch also has an updated ant build which works with the new maven 
directory structure.

To merge the changes back into trunk, just run the follow in a clean trunk 
checkout:

[code}
svn merge -r 679094:679134 
https://svn.apache.org/repos/asf/activemq/sandbox/zookeeper
{code}
  
> 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