Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 6 Sep 2013 01:48:51 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12596131.1340820825992.89325.1378432131952@arcas>
In-Reply-To: <JIRA.12596131.1340820825992@arcas>
References: <JIRA.12596131.1340820825992@arcas>
Subject: [jira] [Commented] (ACCUMULO-658) refactor code into separate
 modules where appropriate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF subversion and git services commented on ACCUMULO-658:
----------------------------------------------------------

Commit bc0aaf426bb33564d4455c9d03be574ef941ec15 in branch refs/heads/ACCUMULO-210 from [~ctubbsii]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=bc0aaf4 ]

ACCUMULO-658 Ignore missing license headers on monitor resources

                
> refactor code into separate modules where appropriate
> -----------------------------------------------------
>
>                 Key: ACCUMULO-658
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-658
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Adam Fuchs
>            Assignee: Christopher Tubbs
>
> This ticket is a parent of several other tickets, under which we can discuss the merits of separating or grouping particular modules into more or fewer maven projects. Here's a list of pros and cons:
> h6. Pros:
> * Explicit modularity encourages reuse outside of Accumulo.
> * Smaller projects encourage participation in coding project-local features.
> * Projects like the shell and the monitor can be exemplars for new projects or applications built on top of Accumulo.
> * Separating projects forces use of publicly accessible APIs instead of custom connections. This is a form of dogfooding, and helps code quality.
> h6. Cons:
> * More projects means more maven configuration, particularly in downstream projects that are dependent on multiple projects.
> * Coding features across projects might be harder to comprehend and to test.
> * In the extreme case, we may see public API bloat in order to support too diverse a set of projects.
> Discuss...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira