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] Commented: (HBASE-2099) Move build to Maven
Date Tue, 12 Jan 2010 01:56:54 GMT

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

Paul Smith commented on HBASE-2099:

i managed to make some progress here by being.... crafty (ok it's a hack, lets be honest).

What I've started down the path of doing is simply adding a 'core' subdirectory under the
main hbase trunk check out. inside that directory is just a pom.  using judicious references
to "${basedir}../src/java" etc I can fake out Maven into thinking that the core is a true

Still, my main headache is finding a binary for thrift, can't spot that anywhere, and indeed
the ivy.xml currently has a commented out block for zookeeper and ivy (i've got a local zookeeper
binary in our corporate Nexus maven repo so I'm just leveraging off that one for now ).

I suspect we would also need to split out a resource directory, currently the following files
under src/java wouldn't end up in the final jar without some more directory moving or trickery:

bash-3.2$ find src/java/ -type f | fgrep -v '.java' | fgrep -v '.svn'

If we could move these to say, src/resources, then it's pretty simple, just tell Maven that's
the resource directory and it gets added to the jar.

I'll keep working on it, but I feel fairly close to the core part being done.  After that,
I'll make sure the contrib compiles and packages nicely, then I'll need to cycle back and
make sure the test cycle is working ok.  

> Move build to Maven
> -------------------
>                 Key: HBASE-2099
>                 URL: https://issues.apache.org/jira/browse/HBASE-2099
>             Project: Hadoop HBase
>          Issue Type: Task
>            Reporter: stack
> 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