[
https://issues.apache.org/jira/browse/GORA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063259#comment-14063259
]
Rob Vesse commented on GORA-357:
--------------------------------
Lewis, one option that comes to mind that I've used in other Maven projects in
the past is to use Maven profiles
Tests that are environment specific/long running that only core developers
should care about get split into separate module(s) which are only built if the
user explicitly invokes a specific developer profile e.g.
{noformat}
mvn clean install
{noformat}
Would just build standard modules and run normal tests.
{noformat}
mvn clean install -Pdev
{noformat}
Would build the complete stack including any environment specific/slow
running/core dev only tests
> Maven Surefire testFailureIgnore is true
> ----------------------------------------
>
> Key: GORA-357
> URL: https://issues.apache.org/jira/browse/GORA-357
> Project: Apache Gora
> Issue Type: Bug
> Components: build process
> Reporter: Tyler Palsulich
> Priority: Minor
>
> The root pom.xml file has the following line:
> {{<testFailureIgnore>true</testFailureIgnore>}}. I've noticed that some unit
> tests fail on a clean install (e.g.
> gora.avro.mapreduce.TestDataFileAvroStoreMapReduce). Is this to be expected?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
