From 41b69d8fb02b8fcaab5c43e8909f92bf8f65d7ef Mon Sep 17 00:00:00 2001 From: Cristian Date: Thu, 17 Jul 2025 15:54:36 -0300 Subject: [PATCH 01/18] W-18759737-workspace-differences-CP --- .../ROOT/pages/int-migrate-studio-to-acb.adoc | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index fa5ac0c0c..60990c513 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -18,6 +18,33 @@ include::partial$acb-project-migration.adoc[tag="exporting-considerations-from-s include::partial$acb-project-migration.adoc[tag="import-mule-project-into-acb"] +== Understand Workspaces Differences + +An IDE workspace is a logical environment that groups your projects. It also contains all associated settings, configurations, and state for development. Workspaces are primarily used for: + +* Managing multiple related projects +* Keeping plugin-specific settings and environments consistent +* Isolating different development contexts + +=== Workspace Considerations + +Anypoint Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location. Take into account these other considerations when migrating your project: + +* Make sure Anypoint Code Builder supports the Mule runtime version of your project +* Install relevant extensions, if requested +* Configure Git for your projects, if needed +* Set up any custom build configurations, if needed + +=== Verify Workspace Setup + +After importing your project into Anypoint Code Builder, verify the setup is correct: + +* Maven dependencies must resolve correctly +* Run `mvn clean package` to make sure the project builds successfully +* Test that your Mule application runs properly in the new Anypoint Code Builder workspace +* Set up debug configurations if needed to troubleshoot your application +* Check for errors and make sure that the configuration XML file and the canvas load correctly to verify that component dependencies resolve correctly + == See Also * xref:int-import-mule-project.adoc[] From 633bbacd8d39ec1d1dbe244adec7be00ed1040e8 Mon Sep 17 00:00:00 2001 From: Cristian Date: Thu, 17 Jul 2025 16:31:08 -0300 Subject: [PATCH 02/18] W-18759737-workspace-differences-CP --- .../ROOT/pages/int-migrate-studio-to-acb.adoc | 33 ++++++++++++++++--- 1 file changed, 28 insertions(+), 5 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 60990c513..c60454a06 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -35,15 +35,38 @@ Anypoint Studio uses an Eclipse workspace that contains multiple projects. Anypo * Configure Git for your projects, if needed * Set up any custom build configurations, if needed +=== Import Studio Workspace into Anypoint Code Builder + +Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code workspace. + +. In Anypoint Code Builder, go to *File* > *Open Folder*. +. Navigate to your Studio workspace. +. Select the individual project folder. Don't select the entire workspace. + +Alternatively, you can export the Studio workspace as a ZIP file and import the project folder directly into Anypoint Code Builder: + +. In Studio, right-click your project and select *Export*. +. Select *General* > *Archive File*. +. Select one or more projects to export. +. Click *Browse* to select the folder where you want to export the ZIP file. +. Click *Finish*. +. In Anypoint Code Builder, open the *Command Palette* (Ctrl+Shift+P). +. Select *MuleSoft: Import a Mule project*. +. Select *From compressed file*. +. Select the exported ZIP file. + === Verify Workspace Setup After importing your project into Anypoint Code Builder, verify the setup is correct: -* Maven dependencies must resolve correctly -* Run `mvn clean package` to make sure the project builds successfully -* Test that your Mule application runs properly in the new Anypoint Code Builder workspace -* Set up debug configurations if needed to troubleshoot your application -* Check for errors and make sure that the configuration XML file and the canvas load correctly to verify that component dependencies resolve correctly +* The `pom.xml` file is compatible with Anypoint Code Builder +* The Mule runtime version is supported in Anypoint Code Builder +* The Maven dependencies resolve correctly +* The project builds successfully after running `mvn clean package` +* Your Mule application runs as expected in the new Anypoint Code Builder workspace +* Debug configurations are set up to troubleshoot your application +* The configuration XML file show no errors +* The canvas loads correctly, which means that the component dependencies resolve correctly == See Also From 5d237910df3cb42f7d673f39fa516255734c5b41 Mon Sep 17 00:00:00 2001 From: Cristian Date: Thu, 17 Jul 2025 17:45:09 -0300 Subject: [PATCH 03/18] W-18759737-workspace-differences-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index c60454a06..d5bd1cedf 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -50,9 +50,8 @@ Alternatively, you can export the Studio workspace as a ZIP file and import the . Select one or more projects to export. . Click *Browse* to select the folder where you want to export the ZIP file. . Click *Finish*. -. In Anypoint Code Builder, open the *Command Palette* (Ctrl+Shift+P). -. Select *MuleSoft: Import a Mule project*. -. Select *From compressed file*. +. In Anypoint Code Builder, open the *Command Palette*. +. Select *MuleSoft: Import a Mule project* and *From compressed file*. . Select the exported ZIP file. === Verify Workspace Setup From abfab1c62ce6591ea55d85c2a6ddd3f5d8504d19 Mon Sep 17 00:00:00 2001 From: Cristian Date: Thu, 17 Jul 2025 17:46:39 -0300 Subject: [PATCH 04/18] W-18759737-workspace-differences-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index d5bd1cedf..e67083606 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -43,7 +43,7 @@ Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code wo . Navigate to your Studio workspace. . Select the individual project folder. Don't select the entire workspace. -Alternatively, you can export the Studio workspace as a ZIP file and import the project folder directly into Anypoint Code Builder: +Alternatively, you can export the Studio workspace as a ZIP file and import the project folder directly into Anypoint Code Builder. . In Studio, right-click your project and select *Export*. . Select *General* > *Archive File*. @@ -56,7 +56,7 @@ Alternatively, you can export the Studio workspace as a ZIP file and import the === Verify Workspace Setup -After importing your project into Anypoint Code Builder, verify the setup is correct: +After importing your project into Anypoint Code Builder, verify the setup is correct. * The `pom.xml` file is compatible with Anypoint Code Builder * The Mule runtime version is supported in Anypoint Code Builder From c21179429daed834c0956f90b006ad794f237437 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Thu, 17 Jul 2025 17:51:08 -0300 Subject: [PATCH 05/18] W-18759737-Address-vale-CP W-18759737-Address-vale-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index e67083606..f33eb3922 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -28,7 +28,7 @@ An IDE workspace is a logical environment that groups your projects. It also con === Workspace Considerations -Anypoint Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location. Take into account these other considerations when migrating your project: +Anypoint Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location. Evaluate these other considerations if migrating your project: * Make sure Anypoint Code Builder supports the Mule runtime version of your project * Install relevant extensions, if requested @@ -40,7 +40,7 @@ Anypoint Studio uses an Eclipse workspace that contains multiple projects. Anypo Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code workspace. . In Anypoint Code Builder, go to *File* > *Open Folder*. -. Navigate to your Studio workspace. +. Go to your Studio workspace. . Select the individual project folder. Don't select the entire workspace. Alternatively, you can export the Studio workspace as a ZIP file and import the project folder directly into Anypoint Code Builder. @@ -56,7 +56,7 @@ Alternatively, you can export the Studio workspace as a ZIP file and import the === Verify Workspace Setup -After importing your project into Anypoint Code Builder, verify the setup is correct. +After importing your project into Anypoint Code Builder, verify that the setup is correct. * The `pom.xml` file is compatible with Anypoint Code Builder * The Mule runtime version is supported in Anypoint Code Builder From c7ab7126e2af0f8169a5739c7a38364914835c06 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Fri, 22 Aug 2025 15:50:12 -0300 Subject: [PATCH 06/18] W-18759737-Add-link-to-VSCode-help-CP W-18759737-Add-link-to-VSCode-help-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index f33eb3922..56b8ddecd 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -70,3 +70,5 @@ After importing your project into Anypoint Code Builder, verify that the setup i == See Also * xref:int-import-mule-project.adoc[] +* https://code.visualstudio.com/docs/editing/workspaces/workspaces[Visual Studio Code Workspace] + From 1d6dde006ebe2dd4f7c5ea6a69f251880b4c39e2 Mon Sep 17 00:00:00 2001 From: Cristian Date: Fri, 22 Aug 2025 17:26:22 -0300 Subject: [PATCH 07/18] W-18759737-Add-info-to-workspace-article-CP --- .../ROOT/pages/int-migrate-studio-to-acb.adoc | 38 ++++++++++++++++--- 1 file changed, 32 insertions(+), 6 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 56b8ddecd..567febdcf 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -18,7 +18,7 @@ include::partial$acb-project-migration.adoc[tag="exporting-considerations-from-s include::partial$acb-project-migration.adoc[tag="import-mule-project-into-acb"] -== Understand Workspaces Differences +== Understand Workspaces An IDE workspace is a logical environment that groups your projects. It also contains all associated settings, configurations, and state for development. Workspaces are primarily used for: @@ -28,12 +28,21 @@ An IDE workspace is a logical environment that groups your projects. It also con === Workspace Considerations -Anypoint Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location. Evaluate these other considerations if migrating your project: +* Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location as your Studio workspace. +* All your projects within a workspace must use the same Mule runtime and Java version. -* Make sure Anypoint Code Builder supports the Mule runtime version of your project -* Install relevant extensions, if requested -* Configure Git for your projects, if needed -* Set up any custom build configurations, if needed +=== Create a New Workspace + +//TODO: Verify this process. +. In Anypoint Code Builder, go to *File* > *Open Folder*. +. Go to the folder where you want to create your workspace. +. Click *New Folder*. +. Enter a name for your workspace. +. Click *Create*. + +=== Add Projects to a Workspace + +//TODO: Complete this section. Include "How to add configs" in this section if appropriate. === Import Studio Workspace into Anypoint Code Builder @@ -43,6 +52,7 @@ Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code wo . Go to your Studio workspace. . Select the individual project folder. Don't select the entire workspace. +// TODO: If possible, provide only one option for importing the project. Let's choose the happy path. Alternatively, you can export the Studio workspace as a ZIP file and import the project folder directly into Anypoint Code Builder. . In Studio, right-click your project and select *Export*. @@ -67,6 +77,22 @@ After importing your project into Anypoint Code Builder, verify that the setup i * The configuration XML file show no errors * The canvas loads correctly, which means that the component dependencies resolve correctly +=== Troubleshooting Migration Issues + +==== Canvas Loading Issues + +If the canvas is stuck loading flows, update your Mule projects in the workspace to use the same Java and Mule runtime versions. See xref:int-version.adoc#select-mule-and-java-versions-for-a-project[Select Mule and Java Versions for a Project]. + +==== Mule Runtime or Java Version Issues + +If the IDE shows the *Mule runtime or Java version requires further action* error, this means that the Mule runtime or Java version in the project is not compatible with the IDE. + +. Click *Set Version* to update the Mule runtime or Java version. See xref:int-version.adoc#select-mule-and-java-versions-for-a-project[Select Mule and Java Versions for a Project]. +. After selecting compatible Mule runtime and Java versions, click *Apply*. +. Open the *Mule Config XML* file in your project. ++ +The error disappears, and you can work on your project. + == See Also * xref:int-import-mule-project.adoc[] From 0b3767f9b7a5263e5b2b4c4c1ef1e96b77e6c294 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 26 Aug 2025 10:00:21 -0300 Subject: [PATCH 08/18] W-18759737-Improve-content-CP W-18759737-Improve-content-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 567febdcf..ecde2ac60 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -33,7 +33,6 @@ An IDE workspace is a logical environment that groups your projects. It also con === Create a New Workspace -//TODO: Verify this process. . In Anypoint Code Builder, go to *File* > *Open Folder*. . Go to the folder where you want to create your workspace. . Click *New Folder*. From 9f3cc093fe776231b3fdf96cc307f2136082193f Mon Sep 17 00:00:00 2001 From: Cristian Date: Tue, 26 Aug 2025 10:17:48 -0300 Subject: [PATCH 09/18] W-18759737-Add-more-info-to-help-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index ecde2ac60..5857942d3 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -30,6 +30,7 @@ An IDE workspace is a logical environment that groups your projects. It also con * Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location as your Studio workspace. * All your projects within a workspace must use the same Mule runtime and Java version. +* Define configurations to a workspace by adding them to the `.code-workspace` file. === Create a New Workspace @@ -41,7 +42,9 @@ An IDE workspace is a logical environment that groups your projects. It also con === Add Projects to a Workspace -//TODO: Complete this section. Include "How to add configs" in this section if appropriate. +. In Anypoint Code Builder, go to *File* > *Add Folder to Workspace*. +. Select the folder where you want to add your project. +. Click *Add*. === Import Studio Workspace into Anypoint Code Builder @@ -51,9 +54,9 @@ Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code wo . Go to your Studio workspace. . Select the individual project folder. Don't select the entire workspace. -// TODO: If possible, provide only one option for importing the project. Let's choose the happy path. -Alternatively, you can export the Studio workspace as a ZIP file and import the project folder directly into Anypoint Code Builder. +== Import a Studio Project into Anypoint Code Builder +//TODO: Verify if this explanations is not duplicated. . In Studio, right-click your project and select *Export*. . Select *General* > *Archive File*. . Select one or more projects to export. @@ -84,7 +87,7 @@ If the canvas is stuck loading flows, update your Mule projects in the workspace ==== Mule Runtime or Java Version Issues -If the IDE shows the *Mule runtime or Java version requires further action* error, this means that the Mule runtime or Java version in the project is not compatible with the IDE. +If the Mule runtime or Java version in the project is not compatible with the IDE, it shows a *Mule runtime or Java version requires further action* error. . Click *Set Version* to update the Mule runtime or Java version. See xref:int-version.adoc#select-mule-and-java-versions-for-a-project[Select Mule and Java Versions for a Project]. . After selecting compatible Mule runtime and Java versions, click *Apply*. From 5e3b989d38b239d107ef015e2476fa1c7ced61b2 Mon Sep 17 00:00:00 2001 From: Cristian Date: Tue, 26 Aug 2025 10:20:33 -0300 Subject: [PATCH 10/18] W-18759737-Change-page-layout-CP --- .../ROOT/pages/int-migrate-studio-to-acb.adoc | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 5857942d3..a29fd7dec 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -18,6 +18,18 @@ include::partial$acb-project-migration.adoc[tag="exporting-considerations-from-s include::partial$acb-project-migration.adoc[tag="import-mule-project-into-acb"] +== Import a Studio Project into Anypoint Code Builder + +//TODO: Verify if this explanations is not duplicated. +. In Studio, right-click your project and select *Export*. +. Select *General* > *Archive File*. +. Select one or more projects to export. +. Click *Browse* to select the folder where you want to export the ZIP file. +. Click *Finish*. +. In Anypoint Code Builder, open the *Command Palette*. +. Select *MuleSoft: Import a Mule project* and *From compressed file*. +. Select the exported ZIP file. + == Understand Workspaces An IDE workspace is a logical environment that groups your projects. It also contains all associated settings, configurations, and state for development. Workspaces are primarily used for: @@ -54,18 +66,6 @@ Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code wo . Go to your Studio workspace. . Select the individual project folder. Don't select the entire workspace. -== Import a Studio Project into Anypoint Code Builder - -//TODO: Verify if this explanations is not duplicated. -. In Studio, right-click your project and select *Export*. -. Select *General* > *Archive File*. -. Select one or more projects to export. -. Click *Browse* to select the folder where you want to export the ZIP file. -. Click *Finish*. -. In Anypoint Code Builder, open the *Command Palette*. -. Select *MuleSoft: Import a Mule project* and *From compressed file*. -. Select the exported ZIP file. - === Verify Workspace Setup After importing your project into Anypoint Code Builder, verify that the setup is correct. From c237e84d5949b3e284cfd59abff19b8560664570 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 26 Aug 2025 11:04:33 -0300 Subject: [PATCH 11/18] W-18759737-Delete-duplicated-info-CP W-18759737-Delete-duplicated-info-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index a29fd7dec..c5b6a9ad4 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -18,18 +18,6 @@ include::partial$acb-project-migration.adoc[tag="exporting-considerations-from-s include::partial$acb-project-migration.adoc[tag="import-mule-project-into-acb"] -== Import a Studio Project into Anypoint Code Builder - -//TODO: Verify if this explanations is not duplicated. -. In Studio, right-click your project and select *Export*. -. Select *General* > *Archive File*. -. Select one or more projects to export. -. Click *Browse* to select the folder where you want to export the ZIP file. -. Click *Finish*. -. In Anypoint Code Builder, open the *Command Palette*. -. Select *MuleSoft: Import a Mule project* and *From compressed file*. -. Select the exported ZIP file. - == Understand Workspaces An IDE workspace is a logical environment that groups your projects. It also contains all associated settings, configurations, and state for development. Workspaces are primarily used for: From d57c9f71e0f0d720034806746e3e62fcf9ca0a29 Mon Sep 17 00:00:00 2001 From: Cristian Date: Tue, 26 Aug 2025 11:20:15 -0300 Subject: [PATCH 12/18] W-18759737-Update-content-CP --- .../ROOT/pages/int-migrate-studio-to-acb.adoc | 35 +++++++++++++++++-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index c5b6a9ad4..851ec68af 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -29,8 +29,7 @@ An IDE workspace is a logical environment that groups your projects. It also con === Workspace Considerations * Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location as your Studio workspace. -* All your projects within a workspace must use the same Mule runtime and Java version. -* Define configurations to a workspace by adding them to the `.code-workspace` file. +* All your projects within a workspace must use the same Mule run-time and Java version. === Create a New Workspace @@ -46,6 +45,38 @@ An IDE workspace is a logical environment that groups your projects. It also con . Select the folder where you want to add your project. . Click *Add*. +=== Add Configurations to a Workspace + +Group multiple project folders into one top-level workspace if working on several related projects at one time. + +A workspace configuration file (`.code-workspace`) is created to store workspace-specific settings. This file is located in the root folder. + +To add configurations to your workspace: +. Go to *File* > *Save Workspace As*. +. Select a location for your `.code-workspace` file. +. Open the `.code-workspace` file. +. Add your configurations in JSON format. + +For example, you can define settings that apply to all projects in the workspace: +[source,json] +---- +{ + "folders": [ + { + "path": "project-a" + }, + { + "path": "project-b" + } + ], + "settings": { + "java.home": "/path/to/your/jdk" + } +} +---- + +You can add any VS Code setting to the `settings` section of your `.code-workspace` file. + === Import Studio Workspace into Anypoint Code Builder Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code workspace. From 48508a1223f48bb0663b955bd12cfb55c169f6f2 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 26 Aug 2025 11:21:13 -0300 Subject: [PATCH 13/18] W-18759737-Fix-format-CP W-18759737-Fix-format-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 851ec68af..5dc98a6f8 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -51,7 +51,6 @@ Group multiple project folders into one top-level workspace if working on severa A workspace configuration file (`.code-workspace`) is created to store workspace-specific settings. This file is located in the root folder. -To add configurations to your workspace: . Go to *File* > *Save Workspace As*. . Select a location for your `.code-workspace` file. . Open the `.code-workspace` file. From f0aaa086c62752950e1bc1ad6d0238fbe8efaf40 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 26 Aug 2025 11:25:33 -0300 Subject: [PATCH 14/18] W-18759737-Address-Vale-feedback-CP W-18759737-Address-Vale-feedback-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 5dc98a6f8..7ad57e377 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -105,7 +105,7 @@ If the canvas is stuck loading flows, update your Mule projects in the workspace ==== Mule Runtime or Java Version Issues -If the Mule runtime or Java version in the project is not compatible with the IDE, it shows a *Mule runtime or Java version requires further action* error. +If the Mule runtime or Java version in the project isn't compatible with the IDE, it shows a *Mule runtime or Java version requires further action* error. . Click *Set Version* to update the Mule runtime or Java version. See xref:int-version.adoc#select-mule-and-java-versions-for-a-project[Select Mule and Java Versions for a Project]. . After selecting compatible Mule runtime and Java versions, click *Apply*. From bc53e86b02bfe776fe45b8e8bcc8f067fa58a48e Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 26 Aug 2025 17:56:11 -0300 Subject: [PATCH 15/18] W-18759737-Add-missing-steps-CP W-18759737-Add-missing-steps-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 7ad57e377..7e6ba0545 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -41,9 +41,11 @@ An IDE workspace is a logical environment that groups your projects. It also con === Add Projects to a Workspace -. In Anypoint Code Builder, go to *File* > *Add Folder to Workspace*. +. In Anypoint Code Builder, open the project to add to the Anypoint Code Builder workspace. +. Go to *File* > *Add Folder to Workspace*. . Select the folder where you want to add your project. . Click *Add*. +. Click *Restart Anyway*. === Add Configurations to a Workspace @@ -53,6 +55,7 @@ A workspace configuration file (`.code-workspace`) is created to store workspace . Go to *File* > *Save Workspace As*. . Select a location for your `.code-workspace` file. +. Click *Restart Anyway*. . Open the `.code-workspace` file. . Add your configurations in JSON format. From 05cbca31c12768980569b6c3a12840c53186f064 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 16 Sep 2025 17:09:56 -0300 Subject: [PATCH 16/18] W-18759737-Address-Sujan-feedback-CP W-18759737-Address-Sujan-feedback-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index 7e6ba0545..fe24c97f9 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -28,8 +28,8 @@ An IDE workspace is a logical environment that groups your projects. It also con === Workspace Considerations -* Studio uses an Eclipse workspace that contains multiple projects. Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. So Anypoint Code Builder workspace can be physically in the same location as your Studio workspace. -* All your projects within a workspace must use the same Mule run-time and Java version. +* Anypoint Code Builder uses a folder-based VS Code workspace, typically with one or more projects per workspace. +* All your projects within a workspace must use the same Mule runtime and Java version. === Create a New Workspace From 157cf5ee660b9af327de5df415fa916d78374f87 Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 16 Sep 2025 17:14:58 -0300 Subject: [PATCH 17/18] W-18759737-improve-steps-CP W-18759737-improve-steps-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index fe24c97f9..ccbcd9df0 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -54,7 +54,7 @@ Group multiple project folders into one top-level workspace if working on severa A workspace configuration file (`.code-workspace`) is created to store workspace-specific settings. This file is located in the root folder. . Go to *File* > *Save Workspace As*. -. Select a location for your `.code-workspace` file. +. Select a location for your `.code-workspace` file and click *Save*. . Click *Restart Anyway*. . Open the `.code-workspace` file. . Add your configurations in JSON format. From e00d013ccc49def35fb91e7ff11c6ca8971303ab Mon Sep 17 00:00:00 2001 From: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> Date: Tue, 16 Sep 2025 17:29:33 -0300 Subject: [PATCH 18/18] W-18759737-Remove-a-section-CP W-18759737-Remove-a-section-CP --- modules/ROOT/pages/int-migrate-studio-to-acb.adoc | 8 -------- 1 file changed, 8 deletions(-) diff --git a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc index ccbcd9df0..d204ece59 100644 --- a/modules/ROOT/pages/int-migrate-studio-to-acb.adoc +++ b/modules/ROOT/pages/int-migrate-studio-to-acb.adoc @@ -79,14 +79,6 @@ For example, you can define settings that apply to all projects in the workspace You can add any VS Code setting to the `settings` section of your `.code-workspace` file. -=== Import Studio Workspace into Anypoint Code Builder - -Import your Anypoint Studio workspace into Anypoint Code Builder as a VS Code workspace. - -. In Anypoint Code Builder, go to *File* > *Open Folder*. -. Go to your Studio workspace. -. Select the individual project folder. Don't select the entire workspace. - === Verify Workspace Setup After importing your project into Anypoint Code Builder, verify that the setup is correct.