hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4336) Convert source tree into maven modules
Date Sat, 26 May 2012 21:07:24 GMT

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

Hudson commented on HBASE-4336:
-------------------------------

Integrated in HBase-TRUNK #2926 (See [https://builds.apache.org/job/HBase-TRUNK/2926/])
    HBASE-4336 Convert source tree into maven modules (Revision 1342958)

     Result = FAILURE
stack : 
Files : 
* /hbase/trunk/hbase-assembly/src/assembly/all.xml
* /hbase/trunk/hbase-server/src/main/resources/hbase-webapps/static/hbase_logo_med.gif
* /hbase/trunk/hbase-server/src/test/data
* /hbase/trunk/hbase-server/src/test/data/hbase-4388-root.dir.tgz
* /hbase/trunk/hbase-server/src/test/resources/org/apache/hadoop/hbase/io
* /hbase/trunk/hbase-server/src/test/resources/org/apache/hadoop/hbase/io/hfile
* /hbase/trunk/hbase-server/src/test/resources/org/apache/hadoop/hbase/io/hfile/8e8ab58dcf39412da19833fcd8f687ac
* /hbase/trunk/hbase-site/pom.xml
* /hbase/trunk/pom.xml

                
> Convert source tree into maven modules
> --------------------------------------
>
>                 Key: HBASE-4336
>                 URL: https://issues.apache.org/jira/browse/HBASE-4336
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: Gary Helmling
>            Assignee: Jesse Yates
>            Priority: Critical
>             Fix For: 0.96.0
>
>         Attachments: 4336-addendum-2.txt, 4336-addendum-3.txt, 4336v2.txt.gz, 4336v2_part2.txt,
hbase-4336-addendum.patch, hbase-4336-v1.patch.gz, hbase-4336-v2.patch.gz, refactor.txt.gz
>
>
> When we originally converted the build to maven we had a single "core" module defined,
but later reverted this to a module-less build for the sake of simplicity.
> It now looks like it's time to re-address this, as we have an actual need for modules
to:
> * provide a trimmed down "client" library that applications can make use of
> * more cleanly support building against different versions of Hadoop, in place of some
of the reflection machinations currently required
> * incorporate the secure RPC engine that depends on some secure Hadoop classes
> I propose we start simply by refactoring into two initial modules:
> * core - common classes and utilities, and client-side code and interfaces
> * server - master and region server implementations and supporting code
> This would also lay the groundwork for incorporating the HBase security features that
have been developed.  Once the module structure is in place, security-related features could
then be incorporated into a third module -- "security" -- after normal review and approval.
 The security module could then depend on secure Hadoop, without modifying the dependencies
of the rest of the HBase code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message