[ https://issues.apache.org/jira/browse/HBASE-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089807#comment-14089807 ]
Jonathan Hsieh commented on HBASE-3361: --------------------------------------- i don't think this is correct or relevant any more (this is from 0.92/0.90 days before we modularized the maven build). I'm just going to close this won't fix. > Modularize Maven Structure for Tests > ------------------------------------ > > Key: HBASE-3361 > URL: https://issues.apache.org/jira/browse/HBASE-3361 > Project: HBase > Issue Type: Improvement > Components: documentation > Reporter: Ed Kohlwey > Assignee: Misty Stanley-Jones > Attachments: HBASE-3361.patch > > > There's a few reasons to break tests out into their own module: > 1. Allowing maven users to easily re-consume test utilities as part of a > "test" package which doesn't pollute the runtime classpath > 2. Putting integration tests (tests that create or require a cluster) in > their own module allows users to easily rebuild and test the core of HBase > without running long-running tests, reducing the developer iteration loop > After some discussions with Stack on IRC, it sounds like there was some > historic investigation of this which was abandoned because the module system > was becoming too complex. I'd suggest that rather than trying to break out > components all at once into their modules, evaluate creation of modules on a > case-by-case basis and only create them when there's a significant use case > justification. > I created a sample of what I'm thinking about (based on the current trunk) > and posted it on github > git://github.com/ekohlwey/modularized-hbase.git -- This message was sent by Atlassian JIRA (v6.2#6252)