You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Organize your Mule projects, API specifications, and agent networks in workspaces to ensure all Anypoint Code Builder features work correctly. Workspaces help you manage multiple related projects and avoid build-time and design-time issues.
6
+
Organize your Mule projects in workspaces to ensure all Anypoint Code Builder features work correctly. Workspaces help you manage multiple related projects and avoid build-time and design-time issues.
7
7
8
8
[[valid-setups]]
9
9
== Valid Setups for Anypoint Code Builder
@@ -13,12 +13,12 @@ Anypoint Code Builder requires one of the following project configurations to fu
13
13
* A single Mule project open at the root of your directory
14
14
* A multi-root workspace pointing directly to one or more Mule projects
15
15
16
-
If your directory structure doesn't meet these requirements, Anypoint Code Builder displays a message with steps to resolve the issue, such as opening a Mule project or creating a workspace.
16
+
If your directory structure doesn't meet these requirements, Anypoint Code Builder displays a message with steps to resolve the issue, such as opening a Mule project or creating a workspace. See <<fix-nested-project>>.
17
17
18
18
[[create-project-workspace]]
19
19
== Create a Project in a Workspace
20
20
21
-
When you create a new project (API specification, integration, or agent network), add it to a workspace. This setup enables you to add more projects later without restructuring your environment.
21
+
When you create a new project, add it to a workspace. With this setup you can add more projects later without restructuring your environment.
22
22
23
23
To create a project in a workspace:
24
24
@@ -69,7 +69,7 @@ You can open or switch between workspaces using the menu, the Command Palette, o
69
69
+
70
70
* From the menu bar, select *File* > *Open Workspace from File...*.
71
71
* From the Command Palette, run the command `File: Open Workspace from File...`.
72
-
. Navigate to your home directory or the location where you saved the `.code-workspace` file, and select it.
72
+
. Navigate to the location where you saved the `.code-workspace` file (for example, your home directory or a dedicated workspaces folder), and select it.
73
73
+
74
74
The projects open in the Explorer view, and the folder name for the workspace includes *(WORKSPACE)* to indicate that you're working in a multi-root workspace:
75
75
+
@@ -106,7 +106,7 @@ Anypoint Code Builder organizes actions based on their scope:
106
106
| Action Type | Location
107
107
108
108
| *Global actions*
109
-
| Always available from the Command Palette. These actions don't depend on a specific project, such as creating a new project, importing assets from Exchange, or opening ACB settings.
109
+
| Always available from the Command Palette. These actions don't depend on a specific project, such as creating a new project, importing assets from Exchange, or opening Anypoint Code Builder settings.
110
110
111
111
| *Project-specific actions*
112
112
| Available from the context menu (right-click) in the Explorer view. These actions apply to a specific project, such as running, debugging, deploying, or exporting a project.
@@ -124,6 +124,35 @@ VS Code stores workspace configuration in a file with the `.code-workspace` exte
124
124
The `.code-workspace` file must not reside within any of your project folders. Save it in a separate directory, such as your home directory or a dedicated workspaces folder.
125
125
====
126
126
127
+
[[fix-nested-project]]
128
+
== Fix a Nested Project Error
129
+
130
+
This error appears when you open a folder that contains your Mule project instead of opening the project directly, and that folder isn't configured as a multi-root workspace.
131
+
132
+
To fix this issue, open the project folder at the root level or add it to a multi-root workspace.
133
+
134
+
=== Open the Project at the Root
135
+
136
+
If you're working with a single project, open it directly so it appears at the top level of the Explorer view.
137
+
138
+
. From the menu bar, select *File* > *Open Folder...*.
139
+
. Navigate to your Mule project's root folder (the folder containing the `pom.xml` file).
140
+
. Select the folder and click *Open*.
141
+
+
142
+
The project now appears at the top level of the Explorer view, and Anypoint Code Builder features are available.
143
+
144
+
=== Add the Project to a Multi-Root Workspace
145
+
146
+
If you want to keep your current folder structure or work with multiple projects, create a multi-root workspace that points directly to your Mule project.
147
+
148
+
. From the menu bar, select *File* > *Add Folder to Workspace...*.
149
+
. Navigate to your Mule project's root folder and select it.
150
+
. When prompted, save the workspace file (`.code-workspace`) to a location outside of your project folders.
151
+
+
152
+
The project appears in the Explorer view with the *(WORKSPACE)* indicator, and Anypoint Code Builder features are available.
153
+
154
+
TIP: If you frequently work with multiple projects, creating a workspace from the start avoids this issue. See <<create-project-workspace>>.
155
+
127
156
== See Also
128
157
129
158
* xref:imp-implement-local-apis.adoc[Iteratively Design and Implement APIs]
0 commit comments