[
https://issues.apache.org/jira/browse/HBASE-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631661#comment-14631661
]
Jesse Yates commented on HBASE-14118:
-------------------------------------
Basic Cross version compat testing? So you could test a new version of HBase
against the minicluster from the plugin in the last version. At least, that's
all I can think of right now.
But still would dramatically help us in cutting down non-destructive,
integration test times. For downstreamers, like Phoenix, they wouldn't need to
spin up/down a minicluster for every test (which ends up being a majority of
the time spent in the test).
It just seems like something the hbase project should own too :)
> minicluster maven plugin
> ------------------------
>
> Key: HBASE-14118
> URL: https://issues.apache.org/jira/browse/HBASE-14118
> Project: HBase
> Issue Type: New Feature
> Components: integration tests, util
> Affects Versions: 2.0.0
> Reporter: Jesse Yates
>
> In the [failsafe docs
> |https://maven.apache.org/surefire/maven-failsafe-plugin/usage.html] they
> describe being able to startup a jetty server before your integration tests
> and then bring it down after the tests. We should be able to provide the same
> for the mini-cluster for downstream projects and cross-version compatibility
> testing.
> The folks over in Kiji made this great [plugin
> |https://github.com/kijiproject/hbase-maven-plugin] that lets you do just
> that! We should see about bringing that under the HBase umbrella proper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)