Anypoint Studio 6.4 with 3.9.0 Update Site 2 Runtime Release Notes

December 15, 2017
Build ID: 201712152228


Mule Runtime

Version: 3.9.0

Anypoint Studio

Version: 6.4.2
Build Id: 201712152228


Versions: 3.9.0 - 3.8.3 - 3.8.2 - 3.8.1 - 3.8.0 - 1.7.4 - 1.6.2 - 1.5.3


Version: 1.2.0


Version: 1.6.1 (munit-studio-plugin)


Versions: 4.5.2

SAP Connector

Versions: 3.2.0

What’s New

This release of Studio 6.4.2 includes mainly bug fixes and support for the Anypoint EU infrastructure.

Migration Guide

For first time installment, please refer to Studio 6.4 release notes for hardware requirements and known issues.

From the previous versions of Studio 5.1.0, 5.1.1, 5.2.0, 5.2.1, 5.3.0, 5.4.1, 5.4.2 and 5.4.3, there is no special migration needed, but when opening a previous Workspace with projects that were created with Studio 5.1.0 or older, and which has metadata stored in disk, Studio asks you to perform an update to all the projects so that the Metadata Manager can handle the types and to show the types in your project.

You can easily import all of the external components that you had installed in your old version of Anypoint Studio through a single action. This includes connectors, runtimes, and any other type of extension added through the Anypoint Exchange or the ​Help → Install new software​ menu, as long as there are no compatibility restrictions.

Do this by selecting File→Import and then choose Install→From existing installation.


Then specify the location of your old version of Anypoint Studio in your local drive.

Eclipse Plugin

If you are using Studio as an Eclipse plugin, you can get this version of Studio using the Eclipse update site http://studio.mulesoft.org/r5/plugin.

This allows you to download Anypoint Studio core and third-party components version 6.x.x and with an embedded version of Mule Runtime v3.9.x along with other optional components.
For a detailed description of the update site’s content visit the Studio in Eclipse section.

JIRA Ticket List for Anypoint Studio

Bug Fixes

  • STUDIO-8593 - Idempotent redelivery policy filer flagged as an error when used as child of File or FTP connector

  • STUDIO-8976 - Duplicated XML config files inside classes folder after exporting app

  • STUDIO-10031 - When overriding maven properties used in finalName from the Run Configuration, deployment fails

  • STUDIO-10034 - [SE] Studio Expression component code disappears

  • STUDIO-10043 - Studio isn’t validation application’s XML when order of items are changed

  • STUDIO-10053 - [SE] FTP passive/active mode issue

  • STUDIO-10080 - [SE] Studio Object builder not saving values unless you hit enter before pressing ok in the window

  • STUDIO-10120 - Studio Validation for the TLS context

  • STUDIO-10142 - Studio isn’t validating application XML order of items

  • STUDIO-10203 - [SE] Cluster module namespaces not properly added

  • STUDIO-10233 - Error when updating software: "Unable to read repository at jar:https://exchange2-asset-manager-kprod.s3.amazonaws.com"

  • STUDIO-10238 - MUnit test are showing incorrect errors

  • STUDIO-10265 - Problem with renaming in Studio

  • STUDIO-10345 - Unable to define metadata for Java object generated from wsdl2java


Was this article helpful?

💙 Thanks for your feedback!