diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md index e4490753b1ca1ab239ccbdaff0756ec2d02766c7..13de9385822750683be422055e2795430b5bcfa5 100644 --- a/docs/usage/configuration-options.md +++ b/docs/usage/configuration-options.md @@ -431,6 +431,8 @@ Note: make sure not to mix this up with the term `compatibility`, which Renovate ## deepExtract +Note: the `deepExtract` configuration option is deprecated, and will be removed in a future Renovate release. + If configured to `true`, then dependency extraction will be done using the relevant package manager instead of JavaScript-based parsing. This option applies only to the `gradle` manager. diff --git a/docs/usage/java.md b/docs/usage/java.md index b1325625896af8de6602baa55bbfc73e6f2ae325..c0c58ea5e645551df44a12e49618fbb6c8785cda 100644 --- a/docs/usage/java.md +++ b/docs/usage/java.md @@ -80,6 +80,7 @@ Renovate will search repositories for all `pom.xml` files and processes them ind ## Custom registry support, and authentication Unless using `deepExtract`, Renovate does not make use of authentication credentials available to Gradle. +Note: the `deepExtract` configuration option is deprecated, and will be removed in a future Renovate release. The manager for Gradle makes use of the `maven` datasource. Renovate can be configured to access additional repositories and access repositories authenticated. diff --git a/lib/manager/gradle/readme.md b/lib/manager/gradle/readme.md index 4e449618b4e51770665071f8913ab1b861ec3f84..b7261fb42e8023c83ca682b8d5a9a7b98eb6067e 100644 --- a/lib/manager/gradle/readme.md +++ b/lib/manager/gradle/readme.md @@ -1,5 +1,7 @@ The `gradle` manager's default behavior uses a custom parser written in JavaScript, similar to many others managers. It was initially known as `gradle-lite` but is now integrated into the `gradle` manager and used as default. +Note: the `deepExtract` configuration option is deprecated, and will be removed in a future Renovate release. + If `deepExtract` is configured to `true`, Renovate instead extracts Gradle dependencies by calling a custom Gradle script. The `gradle` binary is then used to extract Maven-type dependencies.