[
https://issues.apache.org/jira/browse/PHOENIX-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933039#comment-13933039
]
Gabriel Reid commented on PHOENIX-130:
--------------------------------------
{quote}
One warning I get (not sure if it's related to your change):
Description Resource Path Location Type
Overriding managed version 1.7 for build-helper-maven-plugin pom.xml
/phoenix-core line 91 Maven pom Loading Problem
{quote}
That could be related to this change, but as far as I can see it's a non-issue.
The version of the build-helper-maven-plugin just doesn't need to be provided
in phoenix-core/pom.xml, as it's already defined in the root pom, but a
property is used in both places, so it's just overriding itself with the same
version (i.e. a no-op). Removing the <version> from the
build-helper-maven-plugin in phoenix-core/pom.xml will get rid of that warning.
> Separate execution of slow (integration) tests from fast unit tests
> -------------------------------------------------------------------
>
> Key: PHOENIX-130
> URL: https://issues.apache.org/jira/browse/PHOENIX-130
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Gabriel Reid
> Fix For: 3.0.0, 4.0.0
>
> Attachments: PHOENIX-130.2-3.0.patch, PHOENIX-130.2-master.patch,
> PHOENIX-130.patch
>
>
> The current collection of automated unit tests and integration tests takes a
> significant amount of time to run (somewhere in the neighborhood of 90
> minutes on my machine).
> I’d like to propose that the automated tests are split up into two groups:
> * unit tests, which don’t make use of a running HBase and run quickly, and
> will be run within the maven test phase
> * integration tests, which do make use of a running HBase and run more
> slowly, and will be run within the maven integration-test phase
> This approach has the advantage that all fast-running unit tests will be run
> before the integration tests, so if there is a minor issue the build will
> fail-fast instead of first running long-running integration tests before
> failing. It also makes it possible to quickly and regularly run “mvn test”
> during development to run all unit tests in a matter of seconds.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
