Merge pull request #583 from mulesoft/W-21215932-Update-Mule-runtime-content-CP

W-21215932-Update-Mule-runtime-content-CP

Author: Crispy-Salesforce

modules/ROOT/pages/_partials/acb-runtime-java.adoc

@@ -1,7 +1,7 @@
 
 //
 // tag::runtime-java-download[]
-You can select any of the supported Mule runtime and Java versions. The IDE saves your version settings to the project's `mule-artifact.json` file.
+You can select from locally available Mule runtime and Java versions. The dropdown shows only the Mule runtime versions that are installed on your local disk, including bundled Mule runtime versions that are available immediately after installation. The IDE saves your version settings to the project's `mule-artifact.json` file. Bundled Mule runtime versions enable instant project opening and design. To install additional Mule runtime versions, use the `MuleSoft: Install Runtime` command.
 // end::runtime-java-download[]
 //
 //
@@ -19,7 +19,7 @@ To set default Mule runtime and Java versions for the projects you create, see x
 
 //
 // tag::runtime-java-notification[]
-The IDE provides a notification if it is necessary to download the selected Mule runtime or Java version for the project. Mule runtime downloads to `${user.home}/AnypointCodeBuilder/runtimes`, and the selected Java version downloads to `${user.home}/AnypointCodeBuilder/java`.
+Projects open instantly using the bundled Mule runtime versions. The IDE provides a notification only if you must download a specific Mule runtime version or Java version for running or debugging your application. The Mule runtime versions download to `${user.home}/AnypointCodeBuilder/runtimes`, and the selected Java version downloads to `${user.home}/AnypointCodeBuilder/java`.
 // end::runtime-java-notification[]
 //
 

modules/ROOT/pages/index.adoc

@@ -45,7 +45,7 @@ MuleSoft hosts this control plane within Canada (North America) data centers.
 +
 MuleSoft hosts this control plane within Japan (APAC) data centers.
 
-Anypoint Platform hosts deployment targets for managed runtimes and related data, including data and metadata about your Mule implementations.
+Anypoint Platform hosts deployment targets for managed Mule runtime versions and related data, including data and metadata about your Mule implementations.
 
 To change the host from the default (US), see xref:start-acb.adoc#change-clouds[Set the Desktop IDE to a Different Control Plane].
 

modules/ROOT/pages/int-create-integrations.adoc

@@ -87,12 +87,13 @@ Partial searches are accepted.
 ====
 . Select a *Mule runtime* and *Java* version. 
 +
+The dropdown shows only the Mule runtime versions that are installed on your local disk, including bundled Mule runtime versions that are available immediately after installation. By default, the latest bundled Mule runtime version (Java 17 compatible) is selected. For Java 8 projects, select Mule runtime version 4.8 (Java 8 compatible, reduced).
++
 //Info about downloads and versioning:
 include::anypoint-code-builder::partial$acb-runtime-java.adoc[tags="runtime-java-download;runtime-version-note;runtime-java-defaults"]
 . Click *Create Project*.
 +
-//Info about download notifications and location:
-include::partial$acb-runtime-java.adoc[tags="runtime-java-notification"]
+Your project opens instantly using the bundled Mule runtime versions. No Mule runtime download is required to start designing your integration. If you need a specific Mule runtime version for running or debugging, you can install it later using the `MuleSoft: Install Runtime` command. See xref:int-versions.adoc#install-additional-runtimes[Install Additional Mule Runtime Versions].
 
 When you create an integration project from scratch or if your project from Exchange does not contain a flow structure (Flow, Subflow, or Error handling component), the canvas provides the option to create one. Otherwise, the canvas generates a graphical representation of the imported asset's components that you can use to start your configuration.
 

modules/ROOT/pages/int-versions.adoc

@@ -4,18 +4,39 @@ include::reuse::partial$java8-eoss-banner.adoc[tag="java8-eoss"]
 //used in procedures::open-project: Open your implementation or integration project//
 Set Mule runtime engine (Mule), Java, and connector versions to use in your projects.
 
-* <<default-versions, Default versions>>: Set default Mule and Java versions to display in version drop-down menus. 
+Anypoint Code Builder includes bundled Mule runtime versions that enable you to open and design projects instantly without mandatory Mule runtime downloads. The IDE uses these bundled Mule runtime versions for editing and DataSense. Exact Mule runtime versions are only required when you run or debug your applications.
+
+* <<bundled-runtimes, Bundled runtimes>>: Learn about the Mule runtime versions included with Anypoint Code Builder.
+
+* <<default-versions, Default versions>>: Set default Mule and Java versions to show in version dropdown menus. 
 
 * Project-level versions: Set versions to use in a specific project.
 ** For Mule and Java versions, see <<project-version-mule-java>>.
-** For connector versions, see <<project-versions-connectors>>.  
+** For connector versions, see <<project-versions-connectors>>.
+
+* <<install-additional-runtimes, Install additional runtimes>>: Download specific Mule runtime versions when needed for run or debug operations.  
+
+[[bundled-runtimes]]
+== Bundled Mule Runtime Versions
+
+Anypoint Code Builder includes two bundled Mule runtime versions that are available immediately after installation:
+
+* **Mule 4.8 (Java 8 compatible)**: A minimal Mule runtime version bundle compatible with all Java 8-based Mule 4.4 and later projects. This Mule runtime version is used for design-time activities with Java 8 projects and serves as the default fallback for legacy applications. You can't use this version to run Mule applications.
+
+* **Latest Runtime (Java 17)**: The most recent supported Mule runtime version (Edge or LTS) bundled with Anypoint Code Builder at the time of release. For example, Mule 4.11. This Mule runtime version supports Java 17 and can be used for both designing and running applications. Projects configured for Mule 4.6, 4.9, and 4.10 are compatible with this bundled Mule runtime version.
+
+The IDE automatically selects the appropriate bundled Mule runtime version based on your project's Java version:
+* Java 8 projects use the bundled 4.8 minimal Mule runtime version
+* Java 17 projects use the latest bundled Mule runtime version
+
+These bundled Mule runtime versions guarantee that the design service can always start and serve the canvas and design-time needs without requiring runtime downloads. Projects open instantly using these bundled Mule runtime versions. Download a specific Mule runtime version if you want to run or debug your application with an exact version that isn't available locally.
 
 [[default-versions]]
 == Select Default Mule and Java Versions
 
 Select the default Mule and Java versions for new implementation and integration projects. The defaults appear in drop-down menus from which you select a version, for example, when creating a project. 
 
-Versions not present in the IDE append a message similar to *downloads upon project creation*. Versions that don't support a feature typically append a message, such as *AsyncAPI implementation unsupported* for Mule 4.4. 
+The dropdown shows only locally available Mule runtime versions, including the bundled ones. Versions that don't support a feature typically append a message, such as *AsyncAPI implementation unsupported* for Mule 4.4. 
 
 You can set a different version at the project level (see <<project-version-mule-java>>).
 
@@ -35,21 +56,29 @@ include::partial$acb-runtime-java.adoc[tags="runtime-java-version-selection"]
 [[project-version-mule-java]]
 == Select Mule and Java Versions for a Project
 
-Set Mule or Java versions for a specific implementation or integration project from *Project Properties*. You can change versions at any time, but it is important to test your projects with the versions you intend to deploy. 
+Set Mule or Java versions for a specific implementation or integration project from *Project Properties*. You can change versions at any time, but test your projects with the versions you intend to deploy. 
+
+The IDE uses bundled Mule runtime versions to open and edit projects immediately. The design service uses the latest Java-compatible Mule runtime version available locally.  Anypoint Code Builder bundles the latest Mule runtime version (for example, 4.11) for Java 17 and a reduced Mule runtime version 4.8 for Java 8. This guarantees that the design service can always start and serve the canvas and design-time needs without requiring runtime downloads.
+
+Because the bundled Mule runtime version is the latest one, you can open and edit any project regardless of its `minMuleVersion` property. The design service uses the latest Java-compatible Mule runtime version available locally for design-time activities. The `minMuleVersion` property in your project's `mule-artifact.json` file is checked only at deployment time. The `minMuleVersion` property specifies the minimum Mule runtime version required to run or deploy the application.
 
 Version settings are important in several scenarios:
 
 * Updating a project to use more current versions
 * Switching to a supported version, for example, for a project that you import into Anypoint Code Builder that uses an unsupported version
-* Adding a version of Mule or Java that is missing from your project
 * Selecting versions of Mule or Java that are compatible with each other
+* Specifying exact Mule runtime versions for run and debug operations
+
+When you run or debug an application, the IDE checks if the exact Mule runtime version specified in your project is available locally. If not, you see a warning dialog that allows you to:
 
+* Continue with the latest compatible local version
+* Open *Project Properties* to select or download the required Mule runtime version
+ 
 [NOTE]
-Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime. Newer Mule runtimes turn on feature flags by default. See xref:mule-runtime::feature-flagging.adoc[]. This can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change.
+Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime version. Newer Mule runtime versions turn on feature flags by default. See xref:mule-runtime::feature-flagging.adoc[]. This can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule runtime version through *Project Properties*, and always run full regression tests after any version change.
 
 When a Mule or Java version isn't set for a project, the IDE's canvas and notifications provide a *Set version* button that opens the *Project Properties* tab. You can also navigate directly to the *Project Properties* tab. 
 
-
 [[project-versions-from-properties]]
 To select Mule and Java versions for a project:
 
@@ -85,3 +114,32 @@ include::partial$acb-runtime-java.adoc[tags="open-project-properties-menu"]
 image::int-project-properties-connectors.png["Connector versions in Project Properties tab"]
 . Select connector versions. You can update Exchange connector versions for compatibility with your project's Mule runtime and Java versions.
 
+[NOTE]
+====
+Connector compatibility is checked against the selected Mule runtime and Java versions. Compatibility issues appear after you apply changes in *Project Properties*.
+====
+
+[[install-additional-runtimes]]
+== Install Additional Mule Runtime Versions
+
+Bundled Mule runtime versions enable instant project opening and design. If you need specific Mule versions for running or debugging your applications, install these additional versions.
+
+To install a specific Mule runtime version:
+
+. Open *Command Palette* by pressing Cmd+Shift+P on Mac, or Ctrl+Shift+P on Windows.
+. Run the command:
++
+[source,command]
+----
+MuleSoft: Install Runtime
+----
++
+. Select the Mule runtime version to install.
++
+The IDE downloads the selected Mule runtime version to `${user.home}/AnypointCodeBuilder/runtimes`.
+
+[NOTE]
+====
+The dropdown in project creation and *Project Properties* shows only locally available Mule runtime versions. After installing additional Mule runtime versions, they appear in these dropdowns for future use.
+====
+

modules/ROOT/pages/ref-acb-commands.adoc

@@ -69,6 +69,13 @@ MuleSoft: Develop an Integration
 MuleSoft: Download Mule Runtime and Java Versions
 ----
 
+* Install a specific Mule runtime version for use with your projects. This command queries available Mule runtime versions and downloads the selected version to your local Mule runtime directory. See also, xref:int-versions.adoc#install-additional-runtimes[Install Additional Mule Runtime Versions].
++
+[source,command]
+----
+MuleSoft: Install Runtime
+----
+
 * Export a shareable JAR file that contains an integration or implementation project. Both types of projects are Mule applications. See xref:int-export-mule-project.adoc#shareable[Export to a Shareable JAR File]. 
 +
 [source,command]

modules/ROOT/pages/troubleshoot-mule-runtime-errors.adoc

@@ -3,16 +3,16 @@
 
 include::reuse::partial$beta-banner.adoc[tag="anypoint-code-builder"]
 
-Anypoint Code Builder bundles a version 4 instance of Mule runtime engine (Mule) to run your integrations and implementations.  
+Anypoint Code Builder includes bundled Mule runtime versions that enable instant project opening and design. When you run or debug applications, the IDE checks for the exact runtime version specified in your project. If the exact version isn't available locally, error dialogs appear to help you resolve the issue.
 
 Don't change the default locations of Mule. If you receive an error that Mule isn't found or installed, configure the Mule Home path.
 
-If configuring your Mule runtime, ensure you're defining the `mule.homeDirectory` property. 
+When you configure Mule runtime, ensure you define the `mule.homeDirectory` property. 
 
 [NOTE]
 The `mule.runtime.muleRuntimesDirectory` and `mule.runtime.muleHome` properties are legacy configurations no longer used.
 
-* *Mule runtimes*: The Mule runtimes are located in the `{yourACBHome}/runtimes` directory. 
+* *Mule runtime versions*: The Mule runtime versions are located in the `{yourACBHome}/runtimes` directory. 
 +
 Default value: `/Users/{user}/AnypointCodeBuilder/runtime`.
 
@@ -62,18 +62,83 @@ image::troubleshoot-download-java-notification.png["Notification showing a reque
 
 Instead of using this feature, you can use the command *Download Mule Runtime and Java Versions*. See xref:anypoint-code-builder::int-versions.adoc[].
 
+== Mule Runtime Version Not Defined
+
+The error *Mule runtime version not defined* occurs when your project doesn't specify a Mule runtime version in the project's `mule-artifact.json` file.
+
+To resolve this issue:
+
+. Click *Open Project Properties* in the error dialog, or run the command `MuleSoft: Open Mule Project Properties`.
+. In *Project Properties*, select a Mule runtime version.
+. Click *Apply*.
+
+== Java Version Not Defined
+
+The error *Java version not defined* occurs when your project doesn't specify a Java version in the project's `mule-artifact.json` file.
+
+To resolve this issue:
+
+. Click *Open Project Properties* in the error dialog, or run the command `MuleSoft: Open Mule Project Properties`.
+. In *Project Properties*, select a Java version.
+. Click *Apply*.
+
+== Mule Runtime Version Not Found (Compatible Version Available)
+
+The error *Mule runtime [version] not found* occurs when you try to run or debug an application, but the exact Mule runtime version specified in your project isn't available locally. However, a compatible local version is available.
+
+To resolve this issue, you have two options:
+
+* **Continue with compatible version**: Click *Continue* to use the latest local compatible version. The dialog shows which version to use.
+* **Select a different version**: Click *Open Project Properties* to select a different local Mule runtime version or install the exact version using the `MuleSoft: Install Runtime` command.
+
+== Mule Runtime Version Not Found (No Compatible Version)
+
+The error *Mule runtime [version] not found* occurs when you try to run or debug an application, but the exact Mule runtime version specified in your project isn't available locally, and no compatible version is available.
+
+To resolve this issue:
+
+. Click *Open Project Properties* in the error dialog.
+. In *Project Properties*, either:
+** Select a locally available Mule runtime version from the dropdown, or
+** Use the `MuleSoft: Install Runtime` command to download the required version.
+. Click *Apply*.
+
+== Java Version Not Found
+
+The error *Java [version] not found* occurs when you try to run or debug an application, but the Java version specified in your project isn't available locally.
+
+To resolve this issue:
+
+. Click *Open Project Properties* in the error dialog.
+. In *Project Properties*, either:
+** Select Java 17 (or another available version) from the dropdown, or
+** Use the `MuleSoft: Download Mule Runtime and Java Versions` command to download the required Java version.
+. Click *Apply*.
+
+== Mule Runtime and Java Version Not Found
+
+The error *Mule runtime [version] and Java [version] not found* occurs when you try to run or debug an application, but both the Mule runtime and Java versions specified in your project aren't available locally.
+
+To resolve this issue:
+
+. Click *Open Project Properties* in the error dialog.
+. In *Project Properties*:
+** Select a locally available Mule runtime version and Java 17 (or another compatible version) from the dropdowns, or
+** Use the `MuleSoft: Install Runtime` command to download the required Mule runtime version, and use the `MuleSoft: Download Mule Runtime and Java Versions` command to download the required Java version.
+. Click *Apply*.
+
 [[reinstall-mule-runtime]]
 == Reinstall Mule Runtime
 
 If your Mule runtime installation becomes corrupted, you can force a reinstallation:
 
 . Close Anypoint Code Builder.
-. Navigate to your Mule runtimes directory: `${user.home}/AnypointCodeBuilder/runtimes`.
+. Navigate to your Mule runtime directory: `${user.home}/AnypointCodeBuilder/runtimes`.
 . Remove or rename the folder for the runtime version you want to reinstall (for example, `mule-4.6.0`).
 . Open Anypoint Code Builder.
 . Select the Mule runtime version from *Project Properties*.
 +
 The IDE downloads and reinstalls the selected version. For details on selecting versions, see xref:int-versions.adoc#project-version-mule-java[Select Mule and Java Versions for a Project].
 
 [NOTE]
-Your projects and other installed runtimes are not affected.
+Your projects and other installed Mule runtime versions are not affected.

modules/ROOT/pages/troubleshooting.adoc

@@ -169,5 +169,5 @@ Remove any folders starting with `salesforce.mule-dx-` or `mulesoftinc.mule-dx-`
 
 [NOTE]
 --
-This procedure removes downloaded Mule runtimes and Java versions. You can re-download them after reinstalling.
+This procedure removes downloaded Mule runtime versions and Java versions. You can re-download them after reinstalling.
 --

modules/ROOT/pages/tut-af-design-am-flights-api.adoc

@@ -35,7 +35,7 @@ image::acb-mulesoft-in-activity-bar.png["MuleSoft icon in the VS Code Activity B
 +
 image::design-api-1.png["Link to Design an API in the MuleSoft panel"]
 +
-If you receive the error *Mule DX API Component was not installed*, wait for Mule runtime to load and for background processes to complete. To monitor background processes, see xref:troubleshoot-loading-errors.adoc[].
+If you receive the error *Mule DX API Component was not installed*, wait for Mule runtime engine to load and for background processes to complete. To monitor background processes, see xref:troubleshoot-loading-errors.adoc[].
 . Configure your API specification project using these values:
 +
 [%header,cols="1a,1a"]