Tom Akehurst

You can already achieve this with Scenarios e.g. ```java wireMockServer.stubFor(get("/once") .inScenario("once") .whenScenarioStateIs(Scenario.STARTED) .willSetStateTo("next") .willReturn(ok("Hello world!")) ); wireMockServer.stubFor(get("/once") .inScenario("once") .whenScenarioStateIs("next") .willReturn(aResponse().withStatus(409)) ); ```

Actually maybe having `src/jetty11` and `src/jetty12` source trees might be the solution. You'd comment out one of them while developing but then keep both, in addition to `src/java` when building...

Looking at your latest changes I'm starting to wonder if this is going to be a bit too painful to develop and maintain going forward. Perhaps it might be worth...

It looks like we can use `MultiPartFormData.Parser` in place of `MultiPartInputStreamParser` albeit with some work as the API isn't the same. Agree status setting is tricky. I've been Googling a...

I suggest for now we prevent the reason setting tests from running when the Jetty version is 12. We can document the fact it doesn't work with Jetty 12, and...

Thanks for this latest update. I've found a simpler way to organise and build this. Will share a branch with you as soon as I've figured out why I've broken...

Here it is: https://github.com/wiremock/wiremock/tree/reta-issue-2395-jetty-12 Are you in the Slack community BTW @reta ?

I think it might be in a releasable state. It'd be good to get a 2nd pair of eyes on it, but I can get one of my team to...

How about you pull my branch into this PR, then I'll squash and merge? That way you'll get properly credited by the OSS gods.

I think we should create separate GA workflows for the main project and Jetty12. Ensuring 11 support is too important to drop it completely from the matrix.