Hello Gradle Team,
We noticed an interesting feature when upgrading to Gradle 5, as an example the build-scan-plugin requires version 2.0.2 of the plugin after upgrading to Gradle 5, and Gradle fails with an error and explanation that the build-scan-plugin’s version is too low and must be bumped to 2.0.2.
We would like to do something similar in our environment with our Gradle plugins, and I wanted to ask here what is the best way to accomplish implementing “plugin version constraints” similar to how the build-scan-plugin is being handled?
Thank you,
Chris Boyd