Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <101805185.224601263421794473.JavaMail.jira@brutus.apache.org>
Date: Wed, 13 Jan 2010 22:29:54 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-2099) Move build to Maven
In-Reply-To: <1775415801.129551262986314353.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799973#action_12799973 ] 

stack commented on HBASE-2099:
------------------------------

Maybe its time to write the list then?  The only downside I see is that if we go w/ ivy, we are in closer alignment with the hadoop parent and adjacent projects.  Another minor downside is the hardwired "website" that maven generates.  Its hard to pull around.  Currently though, we're in alignment with parent project and we're using forrest which is a dog.

Paul, what you think of the circa-2006 criticisms that maven is a time sink and that it'll make our build harder? (e.g. see commentary on spring moving to maven).  Do you think newer maven better?

When I read the ivy site on why ivy and how it compares to maven, I buy neither.  The only arg. that makes sense for me is the one where ant remains the build driver if you go w/ ivy.  Maven does a load of nice stuff for you.

> Move build to Maven
> -------------------
>
>                 Key: HBASE-2099
>                 URL: https://issues.apache.org/jira/browse/HBASE-2099
>             Project: Hadoop HBase
>          Issue Type: Task
>            Reporter: stack
>         Attachments: HBASE-2099.2.full.patch, HBASE-2099.2.patch, HBASE-2099.3.full.patch, HBASE-2099.3.patch, HBASE-2099.patch
>
>
> This issue is for discussing pros and cons of moving hbase build to Apache Maven.
> Maven, if you take on its paradigm, does a lot for you.  There are also a bunch of nice plugins that do nice reports on state of project; findbugs, that nice plugin where you can give out urls that will resolve to lines in source code (a doxygen-like thing ... I've forgotten its name).  Other examples are a docbook plugin that would do the build inline with doc build.  We could start up the hbase book using docbook format and the hbase book would ride along with versions.
> As I see it -- and its a while since I've done this stuff so things may have since changed -- in the way of an easy move to maven is our src/contrib content.  Maven would have these as distinct projects pulling in their hbase dependency or, if you wanted to take on the maven subproject notion, then, hbase would be at same level in build as the contribs -- it would be a subproject too just built before the others.
> Anyone interested in working on this issue?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.