This decision was migrated from the Tech Leads Decision Log as part of a consolidation process. The original decision record can be found here.
Jakub Skoczen Adam Dickmeiss Julian Ladisch
This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.
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 - RMB-785Implementation/Testing/Code Review: Convert GenerateRunner into maven plugin CLOSED 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).
Build changes (new RMB Maven plugin) will be released as new major RMB release (v33)
Other Related Resources
A change to the pom file in itself is not a breaking change. Then all RMB updates would be breaking changes as you at least must point to the "next" version.
For the RMB-785 case where major surgery was required in pom.xml there were also changes to the API. So : clearly a breaking change.
RMB-785 was for RMB 33.0.0.