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 Fri, 15 Jan 2010 05:56:54 GMT

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

Paul Smith updated HBASE-2099:

    Attachment: test-reports.zip

Here's a small zip of the HTML report from the test run after getting most of this to work.

This highlights a couple of things on the current test source:

* org.apache.hadoop.hbase.util.SoftValueSortedMapTest: - this doesn't have any methods to
run, so currently comes up as an error under Maven.  I can't see in the build.xml where this
would be marked as an ignore one, I can add it in to be ignored, but simpler to either move
this class out of the test resource tree (even delete it if it's not useful anymore)

* 2 failures, not sure if they currently happen in trunk or not, perhaps someone more familiar
with Hbase can tell me 

	junit.framework.AssertionFailedError: expected:<false> but was:<true>


	junit.framework.AssertionFailedError: expected:<2000> but was:<3000>

otherwise the test phase looks good, I will now 'assume all is well' with the test cycle under
Maven and move on to packaging.

> 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, 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