hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Kohlwey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3361) Modularize Maven Structure for Tests
Date Thu, 16 Dec 2010 13:35:12 GMT

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

Ed Kohlwey commented on HBASE-3361:
-----------------------------------

Yeah, unfortunately maven does sort of force your hand on these things.

I would imagine downstream users only want the test utilities (thats the only thing I want).
If we just put the tests in hbase-test/src/test then the tests will have access to the test
utilities (located in hbase-test/src/main ) and won't be published with the actual utility
artifact. Based off of your input, this might be the best way to do it.

> Modularize Maven Structure for Tests
> ------------------------------------
>
>                 Key: HBASE-3361
>                 URL: https://issues.apache.org/jira/browse/HBASE-3361
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>            Reporter: Ed Kohlwey
>            Assignee: Ed Kohlwey
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message