Skip to content

Enhance managed dependencies section with synchronization details #10309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 4, 2025
Merged

Enhance managed dependencies section with synchronization details #10309

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
279c595
Enhance managed dependencies section with synchronization details
jdiehl Nov 3, 2025
28a0be1
added link to gradle
jdiehl Nov 3, 2025
10a0177
updated also refguide
jdiehl Nov 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions content/en/docs/refguide/java-programming/managed-dependencies/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
8 changes: 6 additions & 2 deletions content/en/docs/refguide10/java-programming/managed-dependencies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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.

Expand Down