Closed mefellows closed 1 year ago
Cause of this issue is that the plugin was compiled using JDK 17 as it is the required version for pact driver 4.6.0. java 17 is required to run the plugin
Thanks Ali. So do we need to update the JVM Plugin Driver? Do I need to move this bug upstream?
We need some clarifications to figure out. This plugin was compiled using matchers
version 4.6.0 and core
0.4.0, what does that mean for the end users? what is the backward/forward compatibility of the driver? what version of the driver is OK to use for the endusers?
Good questions, and I'm sorry to say ones I can't answer.
@uglyog I had a quick whip through the docs around this but couldn't see if this was addressed. Mind jumping in here?
Pact-JVM matchers
version 4.6.x requires min JDK 17, 4.5.x has min JDK 11. The plugin driver core
0.4.0 requires min JDK 11.
So either document the minimum JDK as 17, or downgrade Pact-JVM matchers
to 4.5.x to get support for JDK 11.
I think minimum JDK 17 is a fair ask.
Running this example results in a plugin failure: See also https://github.com/pact-foundation/pact-go/pull/291
The core issue seems to be:
Wider log: