[
https://issues.apache.org/jira/browse/HBASE-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972110#action_12972110
]
Lars Francke commented on HBASE-3361:
-------------------------------------
I only skimmed over this now, sorry. Lars G. pointed me to this issue.
The tests (and utility classes) can already be reused by adding the "test" or
"tests" (forgot which is correct) classifier. If that's missing it's a bug in
the current pom that needs to be fixed.
About the quite lengthy test runs: I agree it would be nice but at the moment
the unit test coverage isn't really that good (last time I checked) and the
integration tests while lasting long are pretty important. This seems like a
"political" decision and I'm at -1 to reintroduce modules and keep everything
as it is. You can easily just execute the tests you want.
It might very well be that I'm misunderstanding all or parts of the request but
I'm in a hurry right now - sorry :)
> 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.
