Merge pull request #8461 from atennapel/run/4196-jdm-offline-usage

[RUN-4196] Add information about disabling Gradle synchronization

Author: MariaShaposhnikova

content/en/docs/refguide/java-programming/managed-dependencies.md

@@ -195,10 +195,23 @@ If the above options don't work for you, please reach out to [Mendix Support](ht
 
 ## Marketplace Modules
 
-Dependency information is included per module and included in Marketplace Modules. The actual artifacts (`.jar` files) are not part of the module. They are downloaded to the `vendorlib` folder automatically when synchronization is run when the module is imported.
+Dependency information is included for each module and included in Marketplace Modules. Dependencies are downloaded to the `vendorlib` folder automatically when synchronization is run when the module is imported. Artifacts (`.jar` files) will also be included in the exported module packages. These are used if the module is imported in a Studio Pro which has [Gradle synchronization disabled](#disabling-synchronization).
 
 If you have an issue with the managed dependencies of a Marketplace module, you can revert to an earlier version by removing the new version and downloading an earlier version from the Marketplace.
 
+## Offline Usage {#disabling-synchronization}
+
+{{% alert color="info" %}}
+This feature was introduced in Mendix versions 10.16.0, 10.12.7, and 10.6.17.
+{{% /alert %}}
+
+In the Deployment tab of the Studio Pro preferences [Gradle synchronization](/refguide/preferences-dialog/#gradle-synchronization) can be disabled.
+This means that applications can be started even if Studio Pro is offline or in an air gapped environment.
+
+{{% alert color="info" %}}
+This prevents managed dependencies being synchronized, potentially causing compile errors and version conflicts. In addition, you cannot generate SBOMs while Gradle synchronization is disabled. Mendix recommends that air gapped users configure a [custom repository](#custom-repos) instead of relying on disabling Gradle synchronization.
+{{% /alert %}}
+
 ## Troubleshooting
 
 There can be multiple reasons the dependencies cannot be resolved. See the following for some common failure causes with steps on how to fix the issue.

content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md

@@ -54,6 +54,10 @@ This is the directory where new apps are stored. It is used in the [App Settings
 
 ## Deployment Tab {#deployment}
 
+In the **Deployment** tab you can configure various settings related to application deployment.
+
+{{< figure src="/attachments/refguide/modeling/menus/edit-menu/preferences-dialog/preferences-deployment-tab.png" alt="Preferences" width="600" class="no-border" >}}
+
 ### JDK {#jdk}
 
 Here the directories of the Java Development Kit (JDK) for each supported Java version can be selected.
@@ -74,6 +78,14 @@ This setting is visible and effective when the React client is enabled. By defau
 
 ### Build
 
+#### Gradle Synchronization {#gradle-synchronization}
+
+{{% alert color="info" %}}
+This feature was introduced in Mendix versions 10.16.0, 10.12.7, and 10.6.17.
+{{% /alert %}}
+
+This option controls the synchronization of managed dependencies. For more information, see the [Offline Usage](/refguide/managed-dependencies/#disabling-synchronization) section in *Managed Dependencies*.
+
 #### Gradle Directory
 
 A directory where Gradle is located on the computer that you use to deploy the application. The correct directory is usually located automatically.