Should build (pom.xml) changes required by new RMB be considered breaking?

NOTICE

This decision has been migrated to the Technical Council's Decision Log as part of a consolidation effort. See: DR-000018 - Should build (pom.xml) changes required by new RMB be considered breaking?

The Platform team has been working on restructuring RAML-to-Java generation in RMB to remove the need for dependencies at runtime that should be really be compile-time only. See https://folio-org.atlassian.net/browse/RMB-785 for details. From the module implementers viewpoint the following changes will be required in pom.xml:

See RMB readme: https://github.com/folio-org/raml-module-builder#json-schemas-api
See RMB readme: https://github.com/folio-org/raml-module-builder#client-generator
See RMB Upgrading notes: https://github.com/folio-org/raml-module-builder/blob/master/doc/upgrading.md#version-330

The Platform team would like your feedback on whether these changes should be considered breaking (RMB v33) or minor (RMB v32.2).