Execution default-cli of goal au.com.dius:pact-jvm-provider-maven_2.11:3.2.10:verify failed: Expected a HAL+JSON response from the pact broker, but got 'application/hal+json;charset=utf-8'.
The same project executes the tests successfully when I explicitly point to a contract in the broker using and configuring for pactUrl instead.
There's a chance I'm missing something else, in which case I'd be very grateful for assistance.
Hmm, it's not handling the charset. I'll fix that.
On Tue, 19 Jul 2016, 19:29 mikjonsson [email protected] wrote:
- I'm using a setup as described in
https://github.com/DiUS/pact-jvm/tree/master/pact-jvm-provider-maven#verifying-pact-files-from-a-pact-broker-version-311231- When executing mvn au.com.dius:pact-jvm-provider-maven_2.11:verify
it fails with:Execution default-cli of goal
au.com.dius:pact-jvm-provider-maven_2.11:3.2.10:verify failed: Expected a
HAL+JSON response from the pact broker, but got
'application/hal+json;charset=utf-8'.The same project executes the tests successfully when I explicitly point
to a contract in the broker using and configuring for pactUrl instead.There's a chance I'm missing something else, in which case I'd be very
grateful for assistance.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DiUS/pact-jvm/issues/287, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0tst5GyIa5TVazq2vm3wt0VLEG5KfYks5qXJkNgaJpZM4JPiea
.
Fix released with version 3.2.12
Most helpful comment
Hmm, it's not handling the charset. I'll fix that.
On Tue, 19 Jul 2016, 19:29 mikjonsson [email protected] wrote: