---
schema_version: "1"
id: f48c51abc72c62cda8a252423a8138985c37e7b0652dae88527d2a209298a079
title: Update Workspaces in Anypoint Studio
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/studio/update-workspace.md
canonical_url: https://docs.mulesoft.com/studio/update-workspace
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ba1b440d7834c6c7f20c7de8c65b1627d618ac2e8f6e974aee91f835fad17196
description: MuleSoft Documentation Site
latest: true
---
---
product: Studio
---

# Update Workspaces in Anypoint Studio

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When Anypoint Studio runs in a new workspace for the first time, it validates that the components of
the projects in the workspace are updated and compliant with latest Studio 7.12.0 requirements.

To manually validate your workspace navigate to **Help** > **Validate workspace compatibility**.

![Dialog box that provides the possibility to select the updates that you want to perform.](/mulesoft/current/en-us/studio/_images/update-workspaces.png)

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Studio lists all the open projects in your workspace that must update the Mule Maven Plugin version.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Studio lists all the open projects in your workspace that must add the updated Exchange repository.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td>Selecting <strong>Perform update</strong> enables Studio to update the repositories in the <code>pom.xml</code> file of the projects you selected.</td></tr></tbody></table>

## Mule Maven Plugin Update for Workspaces Created With Studio 7.1.x and Earlier Versions

Studio simplifies the configuration of the `mule-artifact.json` file. When packaging your Mule
application, this file is used to identify the application classloader configuration and settings,
and the minimum required Mule runtime engine version required to run your application.

Studio includes a new version of the Mule Maven Plugin that can automatically infer some of this
required metadata. This makes it easier for you to keep track of all the declarations you need to
make when exporting resources.

<table><colgroup><col> <col></colgroup><thead><tr><th><strong>mule-artifact.json</strong> in 7.1.x</th><th><strong>mule-artifact.json</strong> in 7.12</th></tr></thead><tbody><tr><td><div><div><div><pre><code data-lang="json">{
  "configs": [
    "ch-usage-sync.xml"
  ],
  "redeploymentEnabled": true,
  "name": "ch-usage-sync",
  "minMuleVersion": "4.0.0",
  "requiredProduct": "MULE_EE",
  "classLoaderModelLoaderDescriptor": {
    "id": "mule",
    "attributes": {
      "exportedResources": []
    }
  },
  "bundleDescriptorLoader": {
    "id": "mule",
    "attributes": {}
  }
}</code></pre></div></div></div></td><td><div><div><div><pre><code data-lang="json">{
  "minMuleVersion": "4.0.0",
}</code></pre></div></div></div></td></tr></tbody></table>

This simplification reduces the number of declarations you need to monitor during development. A
fully configured `mule-artifact.json` file is still required by Mule runtime engine when executing
the packaged application. You can find the generated `mule-artifact.json` file inside the `target`
directory after packaging.

The plugin inspects the metadata declared in `mule-artifact.json`. If a value is not declared, the
plugin infers it from the application code before packaging. If other metadata is declared, the
plugin uses it to package the application.

If you update to the latest plugin but choose to keep your former descriptor files, you must
manually monitor your descriptor metadata.

When you update a workspace created using Studio 7.1.x and earlier, Studio overwrites your existing
`mule-artifact.json` file. If you have other declarations in `mule-artifact.json` that you want to
preserve (for example, `secureProperties`, or `redeploymentEnabled`), you should back up those files
outside of your workspace, perform the migration, and then restore your old `mule-artifact.json`
files.

Do not to preserve the following declarations:

- `configs`

- `name`

- `requiredProduct`

- `classLoaderModelLoaderDescriptor`

- `bundleDescriptorLoader`

## Exchange Update for Workspaces Created With Studio 7.11.x and Earlier Versions

Because Anypoint Studio 7.12 adds support for comprehensive publication of assets to Exchange, your
projects must add a dependency to the new version of Anypoint Exchange.

When you open a project created with versions earlier than 7.12, Studio adds this new repository to
your project pom.xml file:

```XML
<repository>
  <id>anypoint-exchange-v3</id>
  <name>Anypoint Exchange V3</name>
  <url>https://maven.anypoint.mulesoft.com/api/v3/maven</url>
  <layout>default</layout>
</repository>
```

You must add this new repository to take advantage of the latest publication process to Exchange.

## See Also

- [Mule Application Packaging](https://docs.mulesoft.com/mule-runtime/latest/mmp-concept#mule-application-packaging)

- [Class Loading Isolation](https://docs.mulesoft.com/mule-runtime/latest/about-classloading-isolation)