You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be a very nice feature if the plugin could be configured to only break the build if the breaking change was not flagged via an increase in the major version of the pom.
That is:
If the new flag, say useSemanticVersioning, is set to true then the plugin should examine if A) the pom version number seems to adhere to the standards of semantic versioning and B) if there has been an increase in the major version as compared to the previous version against which the breaking changes check is performed. If the major version has been increased the developer seems aware of the breaking change for which reason the plugin should allow the build to pass.
The text was updated successfully, but these errors were encountered:
Yes exactly.
And yes - I think that it is a very good idea to still run the check but instead of breaking the build emit some warning/info about the changes!
Hi again
It would be a very nice feature if the plugin could be configured to only break the build if the breaking change was not flagged via an increase in the major version of the pom.
That is:
If the new flag, say useSemanticVersioning, is set to true then the plugin should examine if A) the pom version number seems to adhere to the standards of semantic versioning and B) if there has been an increase in the major version as compared to the previous version against which the breaking changes check is performed. If the major version has been increased the developer seems aware of the breaking change for which reason the plugin should allow the build to pass.
The text was updated successfully, but these errors were encountered: