hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Francke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2099) Move build to Maven
Date Mon, 01 Mar 2010 15:37:05 GMT

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

Lars Francke commented on HBASE-2099:

Just as a heads up: HBase trunk has already moved to Maven as of a few days ago. This issue
can be closed. We have and had a few follow up issues that deal with the problems that occurred:
HBASE-2267, HBASE-2264, HBASE-2254, HBASE-2250

The blog post you cite is very old and while some of the points still apply a lot of it has
been fixed or gotten better since. Bad metadata isn't a problem exclusive to Ivy and Maven
though but for Ant too. Even more so as a lot of projects don't clearly specify their dependencies
at all. We just can do our best to be good "citizens" and provide good project descriptions
- in this case Maven POMs.

1. The build currently doesn't work under Hudson as a result from the switch from Ivy to Maven
but I expect this'll be sorted out in the coming days/weeks. What local cache directories
do you mean that need cleaning up? I don't think we currently do any cleaning up after the
build so any specifics would be helpful so we can change that.
2. I'm no quite sure I can follow you there but there are Maven plugins help in the test process
in various ways. What exactly are you missing there for HBase? If everything else fails Maven
can run Ant tasks fairly easily. I believe we do this as part of our build process now (JspC).
3. Well...that's obviously true independent of the build system used (Ivy, Maven, Ant, Makefiles,

tar: Maven handles this the same way: http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html#tarLongFileMode
- in the newest patch I chose the "gnu" mode.

> 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.13.patch,
HBASE-2099.14.patch, mvn.out, 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.

View raw message