This message was deleted.
# wiremock-javas
Slackbot
09/01/2023, 8:19 AMThis message was deleted.
o
Oleg Nenashev
09/01/2023, 9:03 AMThere are no changes in the packaging structure, but some extra dependencies were shaded, and there are quite a lot of API changes and dependency updates. Also the artifacts were relocated, so you may potentially get into weird issues if you have upstream dependency on old version
https://github.com/wiremock/wiremock/releases/tag/3.0.0
Oleg Nenashev
09/01/2023, 9:04 AMWhat is important is that we haven't yet tested with this library, so any reports will be appreciated
m
Marcin Grzejszczak
09/01/2023, 9:04 AMOk so that's going to be a mess. I think I would need to support 2 versions at the same time. Do you think that's possible?
Also will WireMock JSON stub 3 work with WireMock 2 and vice versa?
o
Oleg Nenashev
09/01/2023, 9:16 AMThe stub formats are compatible. There are a bunch of new features added so the downgrade we will not always work if you adopt the new features
Oleg Nenashev
09/01/2023, 9:17 AM@Marcin Grzejszczak why would you need to support two versions? The third version is supposed to be a drop in replacement for the most of the use cases, though removal of Java 8 is likely to cause problems
Oleg Nenashev
09/01/2023, 9:19 AMIf you want, we can jump on a call in 2 hours or so to look at what the obstacles are. I would like to find solutions where possible, and to document the rest well
m
Marcin Grzejszczak
09/01/2023, 9:21 AMI don't want to break compatibility. I can't simply upgrade WireMock from 2 to 3 in a minor release of Spring Cloud Contract. So I can expect that there will be users working with WireMock 2 and with WireMock 3. I can even expect them doing gradual migrations from WireMock 2 to WireMock 3 and I don't want to break them
o
Oleg Nenashev
09/01/2023, 9:21 AMUnderstood. Let's see what we can do about it
12 Views