hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-2099) Move build to Maven
Date Fri, 19 Feb 2010 06:47:27 GMT

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

stack updated HBASE-2099:
-------------------------

    Attachment: mvn.out

Paul, any chance of you taking a look at this mvn.out file?

Its doing a bunch of the right things, fast, thats great... but see the WARNINGs on the end
about file length.  E.g:

[WARNING] Entry: hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestWildcardColumnTracker.java
longer than 100 characters.
[WARNING] Entry: hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/transactional/DisabledTestHLogRecovery.java
longer than 100 characters.
[WARNING] Entry: hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/transactional/DisabledTestTransactionalHLogManager.java
longer than 100 characters.

This is macosx.

And it seems like the resultant tar.gz is missing stuff when all is done, no jars make it
into the bundle:

{code}
pynchon-2:x stack$ ls -la
total 128
drwxr-xr-x   9 stack  staff    306 Feb 18 22:46 .
drwxr-xr-x  10 stack  staff    340 Feb 18 22:46 ..
-rw-r--r--   1 stack  staff  11358 Jan 21 16:01 LICENSE.txt
-rw-r--r--   1 stack  staff    293 Jan 21 16:01 NOTICE.txt
-rw-r--r--   1 stack  staff     43 Jan 21 16:01 README.txt
drwxr-xr-x  19 stack  staff    646 Feb 18 13:51 bin
drwxr-xr-x   8 stack  staff    272 Feb 18 21:59 conf
drwxr-xr-x   4 stack  staff    136 Feb 18 22:46 contrib
-rw-r--r--   1 stack  staff  43090 Feb 18 22:38 hbase-0.20.2-SNAPSHOT-bin.tar.gz
pynchon-2:x stack$ find . -name *jar
pynchon-2:x stack$ 
{code}

BTW, your instructions are amazing Paul.  Even a gorilla like myself is able to follow the
bouncing ball.



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


Mime
View raw message