Anypoint Studio 7.5.1 Release Notes

May 21, 2020
Build ID: 202005190133

What’s New

Studio 7.5.1 is a patch release focused on resolving Datasense issues and improving the experience of publishing to Exchange when the publishing of your asset fails:

  • Resolved OutOfMemory exception when deploying an application multiple times.

  • Studio now displays metadata for RAML specifications.

  • Studio now displays specific error information from Design Center when the publishing of an API specification fails.

  • Metadata propagates correctly, even if Studio was installed in a machine that had no previous JVM configuration.

  • Improved experience when republishing an API specification from Studio to Exchange.

Studio 7.5.0 upgraded the Eclipse version used by Studio. If you are upgrading from a Studio 7.4.x or earlier versions, 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)


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 then 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.

Projects Compatibility

Anypoint Studio creates workspaces in which you can group your projects. By default, the first time you open Studio, it creates a default workspace. However, depending on the Studio version you used to create a workspace, it may not be compatible with other versions 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 8GB of free RAM available on a developer workstation. As applications become complex, consider adding more RAM.

  • 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 instructions 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.

  • Restarting Studio while the Git Staging view is opened, causes the Commit Message window to show a black background until clicking on it.

  • The autocompletion feature of the editors does not work in workspaces with spaces.

  • Error propagation fails for API Editor.

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

Solved Issues

  • Fixed issue where Studio did not show specific error information from Design Center when publishing an API specification failed.

  • API Projects no longer need MuleSoft public repositories to be built

  • Fixed issue where the artifactId field in the Publish to exchange window was enabled even if the asset was already published to exchange but had errors.

  • Fixed issue where Studio prevented you from republishing an API to exchange if the API had errors and was already published to Exchange.

  • Fixed issue where Studio did not validate the assetId field in the Publish to Exchange window if it was disabled.

  • Fixed issue where the autocomplete feature of the editor listed configuration folders on Windows.

  • Fixed issue where an application using APIKit threw an OutOfMemory exception when deploying the application multiple times.

  • Fixed issue where Studio did not show metadata for a RAML specification.

  • Fixed issue where the metadata was not being propagated when Studio was installed in a machine that had no previous JVM configuration.

Was this article helpful? Thanks for your feedback!