Anypoint Studio 7.13.0 Release Notes
Anypoint Studio is an Eclipse-based integration development environment for designing and testing Mule applications.
What’s New
-
Studio now supports message flow visualization of a Mule configuration loaded from a dependency to explore and debug shared flows.
-
You can now more easily access DataWeave libraries through the Studio UI.
-
The Exchange Comprehensive Publication features enhance the experience of publishing assets to Exchange.
-
You can now add custom fields from the wizard.
-
You can now create and edit Markdown files and deploy them along with the asset.
-
You can now add an icon to new assets when publishing them to Exchange.
-
-
Studio now shows clearer information on the screen.
-
Dependency version is displayed when adding it to a project.
-
When creating an API Project, you’re now notified that Studio creates the project in Design Center as well.
-
API Console now warns you to turn on the Mocking Service for testing their API.
-
-
The underlying infrastructure has been upgraded to Eclipse 4.23.
-
Support for Apple’s M1 processors.
-
Support for macOS 12.4 (Monterey)
Compatibility
Components Bundled With This Release
| Product | Version |
|---|---|
Mule runtime engine |
4.4.0 |
DataWeave |
2.4.0 |
MUnit |
2.3.11 |
MUnit Studio Plugin |
2.7.8 |
Eclipse |
4.23 |
Maven |
3.6.3 |
Adoptium Eclipse Temurin OpenJDK |
JDK 11 (11.0.15+10) |
Mule Runtime Engine Compatibility
Applications developed in Studio 7.13 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 |
Mule runtime engine 4.2.x |
Yes |
Mule runtime engine 4.3.x |
Yes |
Mule runtime engine 4.4.x |
Yes (Bundled) |
UI Compatibility With Application Deployment Targets
Studio 7.13 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 |
Compatibility With Anypoint Platform Installation Options
Studio 7.13 can integrate with the components of the following platforms:
| Anypoint Platform Installation | Compatible |
|---|---|
US Cloud |
Yes |
EU Cloud |
Yes |
MuleSoft Government Cloud |
Yes |
Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) |
Yes |
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 might not be fully compatible with workspaces created by a different version of Studio.
Projects created using 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
-
Studio bundles two different JDKs:
-
Adoptium Eclipse Temurin OpenJDK 11 (11.0.15+10)
JDK 11 starts and runs Studio and the Mule runtime instance used for tooling. -
Adoptium Eclipse Temurin OpenJDK 8 (8u332-b09)
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.
-
-
Operating Systems
-
macOS 10.15.0 through 12.4
-
Windows 10 (64-bit)
-
RHEL 8.3
-
Ubuntu 18.04 or later LTS
-
|
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. |
|
As Studio cannot run natively on ARM processors, it creates a translation layer to operate. For example, Studio runs through the Apple Rosetta II translation layer. |
Fixed Issues
| Issue | ID |
|---|---|
When editing the component configuration using the Mule Properties view, the flow no longer breaks when commenting on a component. |
W-11061833 |
The Edit button no longer remains available causing redundancy when editing a commented-out component. |
W-11061915 |
The Toggle Comment for commenting on a flow with a commented processor via right click now works as expected. |
W-11064826 |
Toolbar buttons in views no longer disappear after some combination of state and actions. |
Eclipse Bug #572598 |
APIKIt properties referenced from a property file are no longer lost when updating the configuration via the UI. |
W-11307620 |
Studio no longer requests that you add an Exchange repository if it has been disabled in properties. |
W-10964462 |
Documentation generated for the MUnit Tests is coherent with the documentation generated for the application. |
W-10965193 |
Studio no longer displays the Missing Body Expression i.e dw 2.0 error message when using a valid DataWeave script on single-line comments. |
W-11009885 |
Known Issues
| Known Issue | ID |
|---|---|
Commenting out a component removes the flow containing the component from the documentation generated using File > Export Studio Documentation. |
W-11062089 |
Context help wizard is not styled correctly in the dark theme. |
Eclipse Bug #532184 |
The input/output panes of the Transform Message component display an incorrect background color when using the light theme. |
W-10639692 [STUDIO-16841] |