From cb1fbca471dc53e4f52fa02705310916a30eb829 Mon Sep 17 00:00:00 2001 From: Cristian Date: Thu, 10 Sep 2026 17:38:25 -0300 Subject: [PATCH 1/2] W-24132580-Add-view-project-dependencies-feature-CP --- code-builder-home/modules/ROOT/nav.adoc | 1 + .../ROOT/pages/des-create-api-fragments.adoc | 9 ++--- .../ROOT/pages/des-design-grpc-api-spec.adoc | 2 +- .../modules/ROOT/pages/ref-acb-commands.adoc | 2 +- .../modules/ROOT/pages/start-discover-ui.adoc | 2 +- .../start-view-project-dependencies.adoc | 35 +++++++++++++++++++ 6 files changed, 42 insertions(+), 9 deletions(-) create mode 100644 code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc diff --git a/code-builder-home/modules/ROOT/nav.adoc b/code-builder-home/modules/ROOT/nav.adoc index c10ecf612..c142fe116 100644 --- a/code-builder-home/modules/ROOT/nav.adoc +++ b/code-builder-home/modules/ROOT/nav.adoc @@ -9,6 +9,7 @@ ** xref:start-fips-compliance.adoc[Configure FIPS Compliance] ** xref:start-discover-ui.adoc[] ** xref:start-use-command-palette.adoc[] +** xref:start-view-project-dependencies.adoc[] ** xref:start-add-folders.adoc[] ** xref:start-open-output-panel.adoc[] ** xref:start-scm.adoc[] diff --git a/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc b/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc index 462bb2f34..4dfda1faf 100644 --- a/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc +++ b/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc @@ -151,15 +151,11 @@ image::des-add-frag-from-exchange.png["Search for fragment in Assets from Exchan . Select a version of the fragment. + The status bar shows the progress. When complete, you see a message that the selected API fragment was successfully added to the project. -. Verify that the fragment dependency was added by checking the `dependencies` section of the `exchange.json` file, for example: -+ -image::des-verify-frag-from-exchange.png["Verify the fragment dependency in the exchange.json file"] -+ -You can also see the fragment in the Explorer view under Project Dependencies, for example: +. Verify that the fragment appears under *Project Dependencies* in Explorer, for example: + image::des-api-frag-dependencies.png["API fragment in the Explorer view"] + -The fragment files are located in your home directory on your system in the `.exchange_modules` directory, for example, `~/.exchange_modules` (Mac). +For more information, see xref:start-view-project-dependencies.adoc[]. [[add-fragments-to-spec]] == Add an API Fragment to Your API Spec @@ -492,6 +488,7 @@ channels: == See Also +* xref:start-view-project-dependencies.adoc[] * xref:des-publish-api-spec-to-exchange.adoc[] * xref:des-create-api-specs.adoc#test-spec[Test Your API Spec Using the Mocking Service] * xref:des-create-api-fragments.adoc#add-fragment-to-project[Add the API fragment from Exchange] diff --git a/code-builder-home/modules/ROOT/pages/des-design-grpc-api-spec.adoc b/code-builder-home/modules/ROOT/pages/des-design-grpc-api-spec.adoc index 97e0ac4f3..604954649 100644 --- a/code-builder-home/modules/ROOT/pages/des-design-grpc-api-spec.adoc +++ b/code-builder-home/modules/ROOT/pages/des-design-grpc-api-spec.adoc @@ -101,7 +101,7 @@ To use a Protobuf fragment published to Exchange: . Open the Command Palette (Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows). . Select *MuleSoft: Add Fragment dependency from Exchange*. . Search for the Protobuf fragment you need and select the version to add. -. After the dependency is added, the library is available under the project. +. After the dependency is added, the library appears under *Project Dependencies* in Explorer. . In your main `.proto` file, use `import` to reference the library's package and message or service definitions. For example: + [source,protobuf] diff --git a/code-builder-home/modules/ROOT/pages/ref-acb-commands.adoc b/code-builder-home/modules/ROOT/pages/ref-acb-commands.adoc index 22d1e1381..8faefa074 100644 --- a/code-builder-home/modules/ROOT/pages/ref-acb-commands.adoc +++ b/code-builder-home/modules/ROOT/pages/ref-acb-commands.adoc @@ -49,7 +49,7 @@ MuleSoft: Open ACB Settings MuleSoft: Show Welcome ---- -* Open project dependencies in the Explorer view. +* Open project dependencies in the Explorer view. See xref:start-view-project-dependencies.adoc[]. + [source,command] ---- diff --git a/code-builder-home/modules/ROOT/pages/start-discover-ui.adoc b/code-builder-home/modules/ROOT/pages/start-discover-ui.adoc index 15016ea9f..15df935cd 100644 --- a/code-builder-home/modules/ROOT/pages/start-discover-ui.adoc +++ b/code-builder-home/modules/ROOT/pages/start-discover-ui.adoc @@ -12,7 +12,7 @@ image:acb-activity-bar-buttons.png["Activity Bar buttons"] + In addition to Anypoint Code Builder (MuleSoft icon), commonly used items in the Activity Bar include: + -* *Explorer*: Open project files and folders. +* *Explorer*: Open project files, folders, and project dependencies. * *Source Control*: Store your project files. * *Run and Debug*: Run and debug integrations and implementations. * *Extensions*: Open for installations and updates. diff --git a/code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc b/code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc new file mode 100644 index 000000000..8ec39d932 --- /dev/null +++ b/code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc @@ -0,0 +1,35 @@ += Viewing Project Dependencies + +View the Exchange assets a project depends on from Explorer in Anypoint Code Builder. The *Project Dependencies* list shows each asset and version on your project. + +== Before You Begin + +* xref:start-acb.adoc[Set up and access Anypoint Code Builder]. +* Open a project that includes dependencies from Anypoint Exchange. + +== View Project Dependencies + +To open the *Project Dependencies* list: + +// Pointer to Command Palette +include::partial$acb-reusable-steps.adoc[tags="open-command-palette"] +. Select this command: ++ +[source,command] +---- +MuleSoft: Show Project dependencies +---- + +Anypoint Code Builder opens Explorer and expands *Project Dependencies*. Each entry identifies an Exchange asset and its version. Expand an entry to see the files in that dependency. + +If a dependency includes other Exchange assets, those nested dependencies appear under the parent entry. + +Alternatively, expand *Project Dependencies* directly in Explorer. + +Anypoint Code Builder downloads dependency files to the `.exchange_modules` directory in your home directory. The *Project Dependencies* list shows those assets in the IDE. + +== See Also + +* xref:des-create-api-fragments.adoc[] +* xref:start-use-command-palette.adoc[] +* xref:ref-acb-commands.adoc[] From 46fb167e22d06b8df0796ed734a776b32a744412 Mon Sep 17 00:00:00 2001 From: Cristian Date: Thu, 10 Sep 2026 19:53:43 -0300 Subject: [PATCH 2/2] W-24132580-Address-SME-feedback-CP --- .../modules/ROOT/pages/start-view-project-dependencies.adoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc b/code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc index 8ec39d932..f4dec8fc7 100644 --- a/code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc +++ b/code-builder-home/modules/ROOT/pages/start-view-project-dependencies.adoc @@ -20,9 +20,7 @@ include::partial$acb-reusable-steps.adoc[tags="open-command-palette"] MuleSoft: Show Project dependencies ---- -Anypoint Code Builder opens Explorer and expands *Project Dependencies*. Each entry identifies an Exchange asset and its version. Expand an entry to see the files in that dependency. - -If a dependency includes other Exchange assets, those nested dependencies appear under the parent entry. +Anypoint Code Builder opens Explorer and expands *Project Dependencies*. Each entry identifies an Exchange asset and its version. If a dependency pulls in other Exchange assets, expand its entry to see those nested dependencies. Alternatively, expand *Project Dependencies* directly in Explorer.