accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1030) Create a Maven plugin to run MiniAccumuloCluster for integration testing
Date Wed, 30 Oct 2013 23:08:27 GMT


ASF subversion and git services commented on ACCUMULO-1030:

Commit 2bedf7bfecfd2d7945e1573d3f09451e85dc1e17 in branch refs/heads/master from [~ctubbsii]
[;h=2bedf7b ]

Revert "ACCUMULO-1030 - accumulo-maven-plugin skipped with skipTests"

This reverts commit 9d6da9698d7a8ae35fa72ce0b48caa0e8124c497.

This commit was done to fix ACCUMULO-1675, but does not correctly do
that. ACCUMULO-1675 was supposed to skip execution of the plugin on a
project that uses it. It was *NOT* supposed to offer a way to avoid
building the plugin itself. Even if we skip tests in the Accumulo build,
we *still* need to build/package/install/deploy this plugin.

To correctly fix ACCUMULO-1675, we need to modify the plugin itself to
behave differently upon encountering -DskipTests (or another similar
flag) on a project that uses this plugin for integration testing against

> Create a Maven plugin to run MiniAccumuloCluster for integration testing
> ------------------------------------------------------------------------
>                 Key: ACCUMULO-1030
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.6.0
> It would be great for users to be able to start up MiniAccumuloCluster with a maven plugin,
so that they can test their code against Accumulo during the integration test phase of the
Maven lifecycle.
> MiniAccumuloCluster can be started during the pre-integration-test phase of the build
lifecycle, then shut down during the post-integration-test phase.
> This would satisfy use cases similar to how one might start up the jetty-maven-plugin
to test a webapp.

This message was sent by Atlassian JIRA

View raw message