From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

If paparrazi has good reasons to require `7.4.0-rc02+` I don't think you can

You could try the regular exclude rules: <https://docs.gradle.org/current/userguide/dependency_downgrade_and_exclude.html#sec:excluding-transitive-deps>

But if paparazzi calls into 7.4 APIs then it'll most likely fail at runtime

Regular exclude rules do not work with classpath dependencies.

I can do this:
```buildscript {
  dependencies {
    classpath("foo:bar:2") {
      exclude(group = "commons-collections", module = "commons-collections")
    }
  }
}```

(not sure how that'd go for you example but the methods/SDL is present)

```WARNING: Android plugin 7.4.0-rc01 has not been tested with this version of the Android cache fix plugin, although it may work.  We test against only the latest patch release versions of Android Gradle plugin: 7.0.4, 7.1.3, 7.2.2, 7.3.1, 7.4.0-beta02, 8.0.0-alpha03.  If 7.4.0-rc01 is newly released, we may not have had a chance to release a version tested against it yet.  Proceed with caution.  You can suppress this warning with with -Dorg.gradle.android.cache-fix.ignoreVersionCheck=true.```

I guess the exclude rules are not working.

I literally had to solve this very problem
```buildscript {
  dependencies {
    constraints {
      // Some plugins (e.g., Paparazzi) try to quietly upgrade the version of AGP we use.
      classpath('com.android.tools.build:gradle') {
        version {
          strictly agpVersion
        }
      }```
but note that Martin is right, Paparazzi has a good reason for requiring a particular version, so be careful