Anypoint Studio 7.5.0 Release Notes

May 1, 2020
Build ID: 202004290032

What’s New

Studio 7.5.0 improves collaboration in the API development process and introduces new functionality to assist users in the API design process.

  • Import API specifications from Design Center standalone as a dependency.

  • Edit OAS and RAML API specifications in Studio.

  • Use the version control mechanism via EGit to pull, push, and merge changes made to API specifications.

  • Compare changes in API specifications with a new diff view.

  • Upgrade to Eclipse 4.13.

  • AdoptOpenJDK 8 included with Studio.

  • Enhanced UI performance with improvements made to garbage collecting mechanisms, minimized background processes, and lazy UI loading.

  • Deployment support for Anypoint Platform Private Cloud Edition (PCE) version 2.1.0.

This release upgrades the Eclipse version used by Studio. To upgrade to this version you must download a fresh installation of Studio. See Downloading and Installing Anypoint Studio for instructions.

Components Bundled With This Release

Product Version

Mule runtime engine


Apache Maven






MUnit Studio Plugin




Mule Plugin for Maven (MMP)



JDK 8 (jdk8u232-b09)

API Development Changes

Import API Specs

As with earlier versions of Studio, you can still import RAML specifications files from your local filesystem or Design Center to your projects.

You can also import RAML or OAS specifications from Exchange or a Maven repository to your projects as a dependency, and keep a pointer to that dependency to keep up to date with newer versions available. See Import an API Specification from Exchange or Maven for more information.

Edit API Specs
  • You can import a RAML or OAS API specification from Design Center as an editable asset in Studio and keep those changes synchronized with Design Center.
    See Synchronize API Specifications with Design Center.

  • You can also edit RAML or OAS specifications that you imported from Exchange or Maven as your project dependencies.
    See Edit Imported API Specifications in Your Projects in Studio.

  • You can edit RAML specifications that you imported from Design Center or your local files into a Mule project however, these modifications cannot be kept in sync with your Design Center API specs.

Publish API Specs

You can publish edits you made to a RAML or OAS API specification that you imported from Exchange or Maven into a Mule project.
See Edit Imported API Specifications in Your Projects in Studio.


Mule Runtime Engine Compatibility

Applications developed in Studio 7.5 are compatible with the following Mule runtime engine versions:

Mule Runtime Engine Version Compatible

Mule runtime engine 3.8.x


Mule runtime engine 3.9.x


Mule runtime engine 4.1.x


Mule runtime engine 4.2.x


Mule runtime engine 4.3.x

Yes (Bundled)

UI Compatibility With Application Deployment Targets

Studio 7.5 offers a graphical interface to deploy Mule 4 applications to the following application deployment targets:

Application Deployment Target Compatible



On-premises Mule runtime engine instances


Runtime Fabric

You can still deploy to Runtime Fabric by exporting your application in Studio and deploy it separately.

Compatibility With Anypoint Platform Installation Options

Studio 7.5 can integrate with the components of the following platform options:

Anypoint Platform Installation Compatible

US Cloud


EU Cloud


MuleSoft Government Cloud


Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

See configure Private Cloud Edition in Studio for more information.

Workspace Upgrade Requirements

Anypoint Studio creates workspaces in which you can create and group your projects. By default, the first time you open Studio, it creates a default workspace and holds all your projects in it. Your Mule application projects can not be fully compatible with workspaces created by a different version of Studio:

Projects created in a Studio 6.x.x or earlier workspace

These projects are not compatible with Studio 7 because they are Mule 3 projects.

Projects created in a 7.1.x workspace

Because Studio 7.2.0 simplified the configuration of the mule-artifact.json file, if you are importing a project created in a Studio 7.1.x workspace, see Updating Workspaces for instructions to update your project structure to a compatible format.

Projects created in a Studio 7.2.x or later workspace

Projects created in this workspace are fully compatible. You can use a project created in a Studio 7.2.x workspace without performing any extra task.

Hardware Requirements

  • MuleSoft recommends a minimum of 4GB of free RAM available on a developer workstation. As applications become complex, consider adding more RAM.

  • 8GB of memory.

  • 2GHz CPU.

  • 10GB free hard drive space.

Software Requirements



Java Environments

  • AdoptOpenJDK 8

This version of Studio is not compatible with Java 9 or Java 10.

Studio no longer requires Java 8 to launch and run properly. Studio comes bundled with AdoptOpenJDK 8.
You can configure Studio to use your preferred JDK version by following the instruction here.

The only compatibility introduced for Java 11 is when using Mule runtime engine 4.2.0 or later.
If you have projects running on Mule runtime engine 4.2.0 or later, and you want to run them using Java 11, see Change the JDK from Studio to learn how to change the JDK used by Studio to run your projects.

Operating Systems

  • macOS 10.12.0 through 10.15

  • Windows 10 (64-bit)

  • RHEL 7.0

  • Ubuntu 15.04 or later

Running real-time antivirus protection software on your operating system might have a negative impact on Anypoint Studio performance. Although this issue is prominent on Windows, it also occurs on Linux and macOS.

Although the steps to solve these performance issues vary depending on your antivirus software, a typical solution is to either allow or exclude the Anypoint Studio and java executables, the Studio install and workspace filesystem locations, or some combination of both. See examples of solutions for McAfee Viruscan, Windows Defender, and Symantec Endpoint Protection.

Known Issues

  • Users must do a fresh install to upgrade from Studio 7.4.x to Studio 7.5.x.

  • As of November 2019, Studio no longer provides binaries.

  • MUnit Studio plugin 2.1.5 does not work with this version of Studio.

  • Because the metadata propagation works differently in Studio 7, Datasense might display errors if your DataWeave code has references to unknown metadata either because you didn’t define the metadata before writing your code, or because your flow is still incomplete.
    See Understanding How DataSense Uses Mule Event Metadata and Transform Message Component for more information.

  • Custom Policies Editor is not supported in Studio 7.x.

  • Copybook import fails with no message.

  • Copybook import file not copied to the project.

  • The pom.xml file of a running application is not updated when changing dependencies.

  • The payload shown while debugging a Mule application in the debug view is partial but there is no way to view the rest of the payload.

  • Mule plugins with snapshot versions must always be regenerated.

  • Datasense does not work correctly through a proxy on connectors using TCP/IP or connectors which don’t yet support it.

  • You won’t be notified when importing a project with a runtime that is not installed in your Studio installation.

  • When restarting Studio and the Git Staging view was opened, the Commit message window shows a black background until clicking on it.

  • Editor autocompletion lists Studio configuration folders on Windows.

  • Editor autocompletion does not work in workspaces with spaces.

  • Editor autocompletion fails when the include clause starts with //.

  • Error propagation fails for API Editor.

  • Git staging view does not refresh nor allow changes on an API specification that was deleted and reimported.

  • Studio does not show specific error information from Design Center when publishing an API specification fails.

  • API projects need MuleSoft public repositories to be built.

  • To build an API Project without Studio (console or CI/CD), it is a requirement to have a settings.xml file with public MuleSoft repositories.

  • The artifactId field in Publish to exchange is enabled if the asset is already published to exchange but has errors.

  • Studio does not validate the assetId field in the Publish to Exchange UI if it is disabled.

Fixed Issues

  • Studio now shows a warning message when it scaffolds a RAML API specification without resources.

  • Studio now shows a warning when a RAML with multiple local APIs failed to scaffold.

  • You can now verify and select the debug port that you want to use at design time.

  • The login view to Anypoint Platform now allows pasting your password.

  • Fixed issue where the Dataweave preview did not respect the defined CSV metadata.

  • Fixed issue where the Transform Message component did not provide a preview of a COBOL Copybook transformation to JSON.

  • Fixed issue where a hot deployment did not work for DataWeave files.

  • Fixed issue where Studio took a long time to download dependencies of projects.

  • Fixed issue where the Error Handler references were not visually showing.

  • Fixed issue where the Mule debugger detected a java.lang.OutOfMemoryError: GC overhead limit exceeded while fetching a large amount of data with Repeatable file store iterable.

  • Fixed issues with metadata propagation from Anypoint Studio v7.3.5.

  • Fixed issue where Add/Remove mappings did not save to APIkit Router configuration.

  • Fixed issue where the Maven configuration was ignoring plugincustomization (=runtime config).

  • Fixed issue where the Mule runtime engine version was not configurable in Studio 7.4 from 4.2.1 to 4.2.2.

  • Fixed issue where Studio falsely detected file modifications while clicking inside of the "Message Flow" window.

  • Fixed issue where some notifications were showing "Unknown" in Studio.

  • Fixed issue where Studio 7 overrode the wrapper.java.additional property.

  • Fixed issue where some artifacts from parents dependencyManagement sections in Maven were not found.

  • Fixed issue where libraries using libraries in an API specification couldn’t resolve to a valid path.

  • Fixed issue where the Debug perspective did not show a full array for query parameters.

  • Fixed issue where Maven settings were ignored when resolving Maven parents dependencies.

  • Fixed issue where a correct DataWeave call to a Java method showed an error in Studio.

  • Fixed issue where Studio got unresponsive when opening a very big DataWeave transformation.

  • Fixed issue where Error while importing API on Anypoint Studio.

  • Fixed issue where Maven logs were blank for embedded mvn commands.

  • Fixed issue where API Query parameter name was not showing in Anypoint Studio.

  • Fixed issue where connector metadata was not propagated from a Mule domain to an application.

  • Fixed issue where a message field, or some other fields, were not completely displayed.

  • Fixed issue where the Aggregator module had a required name field but it never appeared.

  • Fixed issue while defining metadata in a Transform Message component with an xsd schema file.

  • Fixed issue where Studio preferences menu was showing an incorrect Maven version.

  • Fixed issue where the embedded Maven was not showing Maven logs.

  • Fixed issue where the Debug view did not show multiple headers.

Was this article helpful?

💙 Thanks for your feedback!