I tried many combinations but couldn't make it shorter with the same behavior :(
- ph ---
Just a small hint about the concept of includes/excludes.
A test is executed if and only if it matches any include (or all if there
are no includes) AND doesn't match any exclude.
The problem I see is that
On Fri, 24 Feb 2017 04:32:17 +0100, Paul Hammant wrote:
Thanks João, thanks Robert.
I've taken Robert's snippet and expanded it a little to do what I want:
Diff:
https://github.com/paul-hammant/todobackend-jooby/commit/9626a3155eddbaea74bbf66a3e899b81227842ee
(repo: paul-hammant/todob
Thanks João, thanks Robert.
I've taken Robert's snippet and expanded it a little to do what I want:
Diff:
https://github.com/paul-hammant/todobackend-jooby/commit/9626a3155eddbaea74bbf66a3e899b81227842ee
(repo: paul-hammant/todobackend-jooby* branch: expectations*)
I found that I had to
When you only want to change the pom (not the tests), a set of
executionblocks will do the trick:
org.apache.maven.plugins
maven-surefire-plugin
2.18.1
unit-tests
**/*Unit*.java
I'd say you could add executions to the surefire plugin with different
categories:
https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_JUnit_Categories
Look at this gist (I've omitted some details):
https://gist.github.com/kewne/2b909ab5e8035a4e44e406fa35e3276c
AFAIK
