Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <832607313.359401263958674502.JavaMail.jira@brutus.apache.org>
Date: Wed, 20 Jan 2010 03:37:54 +0000 (UTC)
From: "Paul Smith (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (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:all-tabpanel ]

Paul Smith updated HBASE-2099:
------------------------------

    Attachment: HBase Move Script.txt
                HBASE-2099.7.patch

Attached is the first actual patch I deem worthy for someone to try out, and if successful, I will then mail the hbase-dev list to elicit further feedback.

Please:

# save the HBASE-2099-7.patch somewhere

# Read the HBase Move Script.txt file, it contains some important info at the top if you are an existing Maven user that has a local Repository Manager configured.  If you don't, I think it's (strangely) simpler, but otherwise straightforward.

# Execute the non-commented out patch, svn, and mvn statements on your console in your clean hbase-trunk checkout.

*crosses fingers*

> 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: findbugs.html, findbugs.html, HBase Move Script.txt, HBase Move Script.txt, HBASE-2099.5.patch, HBASE-2099.6.patch, HBASE-2099.7.patch, test-reports.zip
>
>
> 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.