You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 21:28:58 UTC

[jira] [Resolved] (HBASE-5977) Usage of modules

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

stack resolved HBASE-5977.
--------------------------
    Resolution: Fixed
      Assignee: Jesse Yates

Resolving as done. When this issue was being worked on, we were careful making modules. Now we make one at the drop of a hat for all the reasons documented in here... 

Resolving as fixed.

> Usage of modules 
> -----------------
>
>                 Key: HBASE-5977
>                 URL: https://issues.apache.org/jira/browse/HBASE-5977
>             Project: HBase
>          Issue Type: Brainstorming
>          Components: build
>    Affects Versions: 0.95.2
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>         Attachments: Potential-HBase-Module-Descriptions-v1.pdf, Potential-HBase-Modules-v2.pdf
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> With HBASE-4336, HBase will have the ability to add multiple modules for different aspects of the codebase (less tests, see HBASE-4336 for details). We need to set a policy for when modules should be used versus putting the code into a single existing module or dispersed across modules. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)