[
https://issues.apache.org/jira/browse/GORA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Palsulich updated GORA-357:
---------------------------------
Attachment: GORA-357.palsulich.071614.patch
Exactly what I was thinking! Here is a patch. If you run {{mvn test}}, any test
with mongo, hbase, or mapreduce in the package name will be skipped. If you run
{{mvn test -Pdev}} all tests (including those above) will be run.
This is accomplished with a new property -- {{exclude.tests}}. By default, it
is {{%regex\[.*/(mapreduce|hbase|mongodb)/.*\]}}, meaning any file with
mapreduce, hbase, or mongodb as one of it's directories. But, the dev profile
sets it to {{nothing-to-exclude}}.
The Jenkins build will have to add the -Pdev argument in order to still run all
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
> Attachments: GORA-357.palsulich.071614.patch
>
>
> 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)
