Skip to content

v8.1.0
Compare
Choose a tag to compare
@rpalcolea rpalcolea released this 12 Oct 00:01
v8.1.0
7f8991b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Introduce skipped configuration names prefixes

Gradle 6.0 compatibility:

Gradle 6.0 changes the consumption and resolution behavior of configurations from the Java plugin. This version introduces the concept of alternative resolution configurations, which are used here.

Gradle 6.1 deprecates declaring dependencies on compile and runtime configurations

The following changes are made:

  • Update tests to use implementation configuration rather than compile to prevent warnings like:
The compile configuration has been deprecated for dependency declaration. This will fail with an error in Gradle 7.0. Please use the implementation configuration instead.
  • Migrate to core locks should migrate over configurations without an alternative resolution configuration (as introduced in Gradle 6.0) to prevent warnings like:
The runtime configuration has been deprecated for resolution. This will fail with an error in Gradle 7.0. Please resolve the runtimeClasspath configuration instead.

  • LockableConfigurations method should only return configurations without a (safely found) resolution alternative (as introduced in Gradle 6.0)

  • Global locking subproject configurations must be resolvable, consumable, and without a resolution alternative to prevent warnings like:

The compile configuration has been deprecated for consumption. This will fail with an error in Gradle 7.0. Please use attributes to consume the apiElements configuration instead.
  • Do not remove Gradle core locking lockfiles for no-longer locked configurations until dependency update task so that using this new plugin version will not immediately cause file system changes when running ./gradlew clean build
Assets 2
Loading