Contact Us 1-800-596-4880
  1. Homepage
  2. Archived Release Notes

  3. Anypoint Studio 7.15.0 Release Notes

Anypoint Studio 7.15.0 Release Notes

Anypoint Studio is an Eclipse-based integration development environment for designing and testing Mule applications.

May 4, 2023

What’s New

  • Improved performance for customers on Windows by enabling the exclusion of Studio from Windows Defender scans.

  • Enhanced experience when importing API specifications or fragments from Design Center.

  • Easy deployment and redeployment of a Mule App to CloudHub 2.0.

  • Native support for Apple M1 and M2 processors.

  • More and clearer details in the log if the pom.xml file contains an error.

  • Updated .gitignore to show the .mule folder as ignored in the Studio UI.

Compatibility

Components Bundled with This Release

Product Version

Mule runtime engine

4.4

DataWeave

2.4.0

MUnit

2.3.14

MUnit Studio Plugin

2.7.10

Eclipse

4.25

Maven

3.8.6

Adoptium Eclipse Temurin OpenJDK

JDK 11 (11.0.17+8)
JDK 8 (1.8.0_362-b09)

  • JDK 11 starts and runs Studio and the Mule runtime instance used for tooling.

  • JDK 8 is the default JRE for running Mule projects.

You can configure Studio to start using your preferred JDK version by following the Configure Studio to Use Your Own JDK steps.

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

Mule Runtime Engine Compatibility

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

Mule Runtime Engine Version Compatible

Mule runtime engine 3.8.x

No

Mule runtime engine 3.9.x

No

Mule runtime engine 4.1.x

Yes (but this version reached End of Life and is no longer supported)

Mule runtime engine 4.2.x

Yes (but this version reached End of Life and is no longer supported)

Mule runtime engine 4.3.x

Yes

Mule runtime engine 4.4.x

Yes (Bundled)

UI Compatibility with Application Deployment Targets

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

Application Deployment Target Compatible

CloudHub

Yes

On-premises Mule runtime engine instances

Yes

Runtime Fabric

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

Compatibility with Anypoint Platform Installation Options

Studio 7.15.0 can integrate with the components of the following platforms:

Anypoint Platform Installation Compatible

US Cloud

Yes

EU Cloud

Yes

MuleSoft Government Cloud

Yes
See access MuleSoft Government Cloud from Studio for more information.

Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

Yes
Studio 7.15.0 can connect only to PCE 3.0.x, 3.1.x, and 3.2.x.
See configure Private Cloud Edition in Studio for more information.

Workspace Upgrade Requirements

Anypoint Studio enables you to create and organize projects in workspaces. When you first open Studio, it automatically generates a default workspace to store all your projects. Your Mule application projects might not be fully compatible with workspaces of a different version of Studio.

Projects created with Studio 6.x.x are not compatible with Studio 7 because they are Mule 3 projects.

See Update Workspaces for more information.

Hardware Requirements

  • 8GB of memory
    MuleSoft recommends a minimum of 4GB 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

  • Operating Systems

    • macOS 11 through 12.4

    • Windows 10, Windows 11 (64-bit)

    • RHEL 8.3

    • Ubuntu 18.04 or later LTS

Windows 11 and RHEL support is based on Eclipse support matrix. Learn more about Eclipse target environments.

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.

Fixed Issues

Issue Resolution ID

Japanese characters are now correctly encoded in console output.

SE-23640 / W-10742953

You can now comment out existing comments.

W-11743804

Studio now looks for the defined global settings.xml file to resolve the POM dependencies from a remote repository.

W-11791010

Studio no longer throws an error when publishing an API with rulesets to Exchange.

W-12117657

Studio now correctly updates the XML view if you update the Web Service Consumer connector configuration in its UI.

W-10639607

Third-party dependencies are now correctly installed if they are available on the .jar repository folder.

W-11990504

The Try Scope Error Handling Reference is now visible in Studio message flow.

W-11063423

Studio no longer throws a DataWeave validation error if using single quotes in .dwl files.

W-11390568

"<ee:set-payload>#['']</ee:set-payload>" no longer causes compilation error in the http-proxy.xml file.

W-11613254

Studio no longer adds extra characters in the Mule source after uncommenting a component previously commented.

W-12067278

The Publish to Exchange option for an API specification project (OAS) now recognizes the version field correctly.

W-10639409

Conditional breakpoints now work as expected with simple conditions.

W-10639481

Importing Google contacts from a local zip file now scaffolds correctly.

W-10640450

Studio no longer sends the wrong component location to the metadata service.

W-11125816

The Studio debugger now correctly listens to flow triggers when an error occurs in a message flow invoked within an async scope.

W-11938557

The Studio debugger no longer has issues with the VM/JMS connector when using publish operations.

W-11998025

Studio no longer displays the error "Failed to solve flow-ref. Flow '#[payload]' not found" if the flow reference is unaware of the payload value.

W-11999541

The Exchange assets are now deployed to the appropriate child business group when deploying to CloudHub 2.0 and the org ID is not updated in the .pom file.

W-12129094

Studio now correctly handles branch names containing "/" on RAML when importing an API specification from Design Center.

W-12226144

Right-clicking now works correctly after entering and exiting the Search in Exchange view in the Mule Palette.

W-12276360

Known Issues

Known Issue ID

The Context help wizard is not styled correctly in the dark theme.

Eclipse Bug #532184

See Also