The intent, along with all the other similar tests, is to make sure that there isn't any unintentional changes in dependencies. Minor changes to Gradle can result in major changes in dependencies. This and other tests will catch these changes before they get released on accident and cause issues downstream.
Unfortunately it does mean that when a dependency is changed intentional some additional work must be done to update these expected results files. I think the cost is worth the protection. If we find it too onerous in the future we could add a `resetChecks` target that automates the copy and reset of these results files. [ Full content available at: https://github.com/apache/geode/pull/2403 ] This message was relayed via gitbox.apache.org for [email protected]
