hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Smith (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-2099) Move build to Maven
Date Sat, 06 Feb 2010 11:18:28 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Paul Smith updated HBASE-2099:

    Attachment: HBASE-2099.9.patch

latest patch and updated Plan document:

* sources for hbase-core now in properly, now minus the '-core' part (although see previous
comment about a probable better way to achieve this)
* adds transactional and ec2 contrib areas to the binary.
* stargate changed over to a WAR.  Looks like this module is trying to be 2 things (both a
jar and war file).  Would likely prefer to make this a multi-module project so as to produce
both the jar, and the war, it's just much simpler that way (the duopoly of it is a bit odd

stack (or whomever) this patch is worth a kick of the tires, but if it doesn't work, the generated
tar ball this is creating on my local workspace can be gotten here:


Note, in the new  plan, there's a set of steps that attempt to set the svn:ignore.  You'll
need to add the 'target' directory into svn:ignore one by one, if someone knows a smart &
fast way to do this, let me know.

> 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-2099.9.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.

View raw message