Merge branch 'master' into v4.7.x

README.md

@@ -125,7 +125,7 @@ You want to look at: [groovy](consumer/groovy) or [junit](consumer/junit)
 ### (Use Clojure I)
 
 Clojure can call out to Java, so have a look at [junit](consumer/junit). For an example
-look at [example_clojure_consumer_pact_test.clj](https://github.com/pact-foundation/pact-jvm/blob/master/consumer/junit/src/test/clojure/au/com/pact-foundation/pact/consumer/junit/example_clojure_consumer_pact_test.clj).
+look at [example_clojure_consumer_pact_test.clj](https://github.com/pact-foundation/pact-jvm/blob/master/consumer/junit/src/test/clojure/au/com/dius/pact/consumer/junit/example_clojure_consumer_pact_test.clj).
 
 ### I Use some other jvm language or test framework
 

provider/junit/README.md

@@ -616,7 +616,8 @@ JUnit mechanism. Additional reports can be generated from the tests.
 ## Enabling additional reports via annotations on the test classes
 
 A `@VerificationReports` annotation can be added to any pact test class which will control the verification output. The
-annotation takes a list report types and an optional report directory (defaults to "target/pact/reports").
+annotation takes a list report types and an optional report directory (defaults to "target/pact/reports" for Maven
+builds and "build/pact/reports" with Gradle).
 The currently supported report types are `console`, `markdown` and `json`.
 
 For example:

provider/junit/src/test/groovy/au/com/dius/pact/provider/junit/target/HttpTargetSpec.groovy

@@ -44,7 +44,10 @@ class HttpTargetSpec extends Specification {
     httpTarget.setupReporters(verifier)
 
     then:
-    1 * verifier.setReporters { r ->  r*.class*.simpleName == ['AnsiConsoleReporter', 'MarkdownReporter'] }
+    1 * verifier.setReporters { r ->
+      r*.class*.simpleName == ['AnsiConsoleReporter', 'MarkdownReporter']
+      r*.reportDir == ['build/pacts/reports' as File, 'build/pacts/reports' as File]
+    }
   }
 
   @SuppressWarnings('ClosureStatementOnOpeningLineOfMultipleLineClosure')