From 279c59596142077b78227ccd9aa2f9ffb34d3e98 Mon Sep 17 00:00:00 2001 From: Jonathan Diehl <1334574+jdiehl@users.noreply.github.com> Date: Mon, 3 Nov 2025 14:49:55 +0100 Subject: [PATCH 1/3] Enhance managed dependencies section with synchronization details Added information about manual synchronization and managing dependency versions. --- .../refguide10/java-programming/managed-dependencies.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide10/java-programming/managed-dependencies.md b/content/en/docs/refguide10/java-programming/managed-dependencies.md index cc8a77f3c31..65302cc7cd7 100644 --- a/content/en/docs/refguide10/java-programming/managed-dependencies.md +++ b/content/en/docs/refguide10/java-programming/managed-dependencies.md @@ -64,9 +64,13 @@ Exclusions are identified through their [Maven naming convention](https://maven. ## Dependency Synchronization {#dependency-synchronization} -When a change is made to a specified dependency, for example, the dependency is removed or the module is updated from the Marketplace, dependency synchronization will automatically run in the background. +When a change is made to a specified dependency, for example, the dependency is removed or the module is updated from the Marketplace, dependency synchronization will automatically run in the background. Dependency synchronization will also run every time you open your app in Studio Pro. -Dependency synchronization also occurs when you open your app in Studio Pro. +{{% alert color="info" %}} +Each time dependency synchronization is run, Studio Pro retrieves the latest compatible versions of all managed dependencies. If a package receives frequent patches, this can result in regular updates. Since each update must be committed to version control, this may lead to a high volume of commits over time. + +To reduce the frequency of updates and associated version control commits, you can configure your managed dependencies to use exact version numbers. This prevents automatic updates during dependency synchronization and helps maintain a more stable and predictable build environment. +{{% /alert %}} You can trigger a manual synchronization in the menu **App** > **Synchronize dependencies**. You may want to do this, for example, when synchronization failed due to connectivity issues. From 28a0be16f0beb783e2d99406224456a5e56b6f26 Mon Sep 17 00:00:00 2001 From: Jonathan Diehl <1334574+jdiehl@users.noreply.github.com> Date: Mon, 3 Nov 2025 15:22:01 +0100 Subject: [PATCH 2/3] added link to gradle --- .../docs/refguide10/java-programming/managed-dependencies.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide10/java-programming/managed-dependencies.md b/content/en/docs/refguide10/java-programming/managed-dependencies.md index 65302cc7cd7..775618e6ca8 100644 --- a/content/en/docs/refguide10/java-programming/managed-dependencies.md +++ b/content/en/docs/refguide10/java-programming/managed-dependencies.md @@ -67,9 +67,9 @@ Exclusions are identified through their [Maven naming convention](https://maven. When a change is made to a specified dependency, for example, the dependency is removed or the module is updated from the Marketplace, dependency synchronization will automatically run in the background. Dependency synchronization will also run every time you open your app in Studio Pro. {{% alert color="info" %}} -Each time dependency synchronization is run, Studio Pro retrieves the latest compatible versions of all managed dependencies. If a package receives frequent patches, this can result in regular updates. Since each update must be committed to version control, this may lead to a high volume of commits over time. +Each time dependency synchronization is run, Studio Pro retrieves the latest compatible versions of all managed dependencies. If a package receives frequent patches, this can result in regular updates if no exact version is specified. Since each update must be committed to version control, this may lead to a high volume of commits over time. -To reduce the frequency of updates and associated version control commits, you can configure your managed dependencies to use exact version numbers. This prevents automatic updates during dependency synchronization and helps maintain a more stable and predictable build environment. +To reduce the frequency of updates and associated version control commits, you can configure your managed dependencies to use exact version numbers. This prevents automatic updates during dependency synchronization and helps maintain a more stable and predictable build environment. You can read about gradle's version ranges on [gradle.org](https://docs.gradle.org/current/userguide/dependency_versions.html) {{% /alert %}} You can trigger a manual synchronization in the menu **App** > **Synchronize dependencies**. You may want to do this, for example, when synchronization failed due to connectivity issues. From 10a017772bb5ffabbf2f6f0dcdfaececc80e9bc1 Mon Sep 17 00:00:00 2001 From: Jonathan Diehl <1334574+jdiehl@users.noreply.github.com> Date: Mon, 3 Nov 2025 15:22:07 +0100 Subject: [PATCH 3/3] updated also refguide --- .../java-programming/managed-dependencies/_index.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/java-programming/managed-dependencies/_index.md b/content/en/docs/refguide/java-programming/managed-dependencies/_index.md index c2ed89339e7..611dd3af75a 100644 --- a/content/en/docs/refguide/java-programming/managed-dependencies/_index.md +++ b/content/en/docs/refguide/java-programming/managed-dependencies/_index.md @@ -54,9 +54,13 @@ Exclusions are identified through their [Maven naming convention](https://maven. ## Dependency Synchronization {#dependency-synchronization} -When a change is made to a specified dependency, for example, the dependency is removed or the module is updated from the Marketplace, dependency synchronization will automatically run in the background. +When a change is made to a specified dependency, for example, the dependency is removed or the module is updated from the Marketplace, dependency synchronization will automatically run in the background. Dependency synchronization will also run every time you open your app in Studio Pro. -Dependency synchronization also occurs when you open your app in Studio Pro. +{{% alert color="info" %}} +Each time dependency synchronization is run, Studio Pro retrieves the latest compatible versions of all managed dependencies. If a package receives frequent patches, this can result in regular updates if no exact version is specified. Since each update must be committed to version control, this may lead to a high volume of commits over time. + +To reduce the frequency of updates and associated version control commits, you can configure your managed dependencies to use exact version numbers. This prevents automatic updates during dependency synchronization and helps maintain a more stable and predictable build environment. You can read about gradle's version ranges on [gradle.org](https://docs.gradle.org/current/userguide/dependency_versions.html) +{{% /alert %}} You can trigger a manual synchronization in the menu **App** > **Synchronize dependencies**. You may want to do this, for example, when synchronization failed due to connectivity issues.