Anypoint Studio 7.4.1 Release Notes
November 26, 2019
Build ID: 201911261732
Compatibility
Studio Components Compatibility
Studio 7.4 is compatible with the following bundled component/extension versions:
| Product | Version |
|---|---|
Mule runtime engine |
4.1.4 and later |
Apache Maven |
3.3.9 |
DataWeave |
2.2.1 and later |
MUnit |
2.2.0 and later |
APIkit |
1.3.6 and later |
Mule Runtime Engine Compatibility
Applications developed in Studio 7.4 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 |
UI Compatibility With Application Deployment Targets
Studio 7.4.x 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.4 can integrate with the components of the following platform options:
| Anypoint Platform Installation | Compatible |
|---|---|
US Cloud |
Yes |
EU Cloud |
Yes |
MuleSoft Government Cloud |
No |
Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) |
Yes |
Projects Compatibility
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.jsonfile, 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
Software |
Version |
Java Environments |
This version of Studio is not compatible with Java 9, Java 10, or Java 11. The only compatibility introduced for Java 11 is when using Mule runtime engine 4.2.0 or later. Studio still requires Java 8 to launch and run properly. You can install and configure Java 11 on your machine, but make sure to configure this JDK to be used by the embedded 4.2.x runtime running in Studio. |
Operating Systems |
|
|
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
-
MUnit Studio plugin 2.1.5 does not work with Studio 7.4.1
-
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. -
As of November 2019, Studio no longer provides binaries.
-
Custom Policies Editor is not yet supported in Studio 7.
-
Anypoint Studio uses your configured default browser to display web content such as Exchange and the Runtime Manager UI when deploying an application to Anypoint Platform. If your default internet browser does not display this content correctly, configure Studio to use a Mozilla/XULRunner runtime environment as the underlying renderer for the Web UI. See Troubleshooting Issues with Your Default OS Browser for more details.
-
Copybook import fails with no message.
-
Copybook import file not copied to project.
-
The
pom.xmlfile 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 should always be regenerated.
-
Datasense/Runtime not working correctly through proxy on connectors using TCP/IP or connectors which don’t yet support it.
-
When importing a project with a runtime that is not installed in Studio there is no notification to the User.
Bug Fixes
-
Fixed an issue where the debugger would not stop at breakpoints of pre-existing projects that were added into Studio 7.4.0.