Currently we have Spring Cloud Contract Wiremock (docs) that supports WireMock as an HTTP server stub. The problem is that it requires the Cloud BOM to be added to your project.

The question is if we can't move it from SCC down to Spring Framework and provide autoconfigurations in Spring Boot? That would make it much easier for users to integrate with tools like WireMock without the need to use Cloud BOM.

Other, project trying to solve a similar problem is https://github.com/maciejwalkowiak/wiremock-spring-boot

Comment From: simonbasle

We've discussed this within the team and we don't think that is something we're likely to do.

  1. while we agree Spring Cloud BOM is too high level, we feel the Spring Framework is too low-level for this
  2. overall, we want to avoid adding new dependencies and integrations (with the version management baggage that inevitably comes with it)
  3. we feel we won't have the bandwidth to efficiently provide good support for such a feature to our users
  4. while the feature set is simple at first glance, it's likely people will ask for increasingly complex new features (there is already such an issue in Spring Cloud Contracts). This doesn't combine well with the previous point.
  5. there are at least two alternatives in community-maintained projects:

I would understand if the Spring Cloud team was hesitant to point users towards these two alternatives (perhaps because it would appear like you vouch for them), but I think that's likely the best avenue to explore in parallel to phasing this module out of Spring Cloud Contracts.

Note that Spring Boot could be considered a better candidate to alleviate point 1), but the Boot team likely has a similar perspective regarding the other arguments exposed above.