STUDIO-8458 - Add an APIKit version compatible with mule 4 STUDIO-8452 - Add an option to collapse or expand all flows/containers STUDIO-8434 - Review validation connector for mule 4 STUDIO-8406 - Add test connection in SDK generated editor, for extensions that have connection providers STUDIO-8401 - Add Mule extensions to project from exchange STUDIO-8400 - Reduce maven startup/download time (prepackage m2 repo) STUDIO-8377 - Define UI for configuring elements that can be defined inline, globally or by expression STUDIO-8361 - Create a sockets icon for Mule 4 STUDIO-8360 - Rename icons so that they match the name of the generated ones STUDIO-8356 - Use the DisplayName property provided by the extensions to generate the caption STUDIO-8288 - Remove blocks when all elements are in place STUDIO-8141 - Add mechanism to override editors provided by connectors STUDIO-8119 - Add MUnit to studio 7 build when there is a mule 4 working version STUDIO-8093 - POC: Change studio model to use the native XML editor model STUDIO-8066 - Use RAML parser v2 for RAML 0.8
#DOWNLOAD JAR JIRA CLIENT 4.0 CODE#
STUDIO-8059 - Remove datamapper code from studio 7 branch STUDIO-8058 - Load extension from mule server
#DOWNLOAD JAR JIRA CLIENT 4.0 UPDATE#
STUDIO-7767 - Update SAP Connector to generate the new metadata model STUDIO-7675 - Create Metadata request using the new Metadata model STUDIO-7670 - Create a Datasense Mule agent client STUDIO-7669 - Update Studio metadata propagation to use the new metadata model STUDIO-7668 - Define migration strategy for metadata
STUDIO-7667 - Update Metadata explorer to use the new Metadata Data model STUDIO-7666 - POC: Have a mule running in background to make datasense requests STUDIO-7665 - Update studio metadata cache to use the new Metadata model STUDIO-7664 - Update autocompletion to use the new Metadata Model
STUDIO-6797 - Define embedded documentation experience STUDIO-5560 - Make all containers collapsible Mule plugins with snapshot versions should always be regenerated.STUDIO-8716ĭataSense does not work for connectors not shipped with Studio. Running application "Pom.xml" is not updated when changing dependencies. Includes are not resolved correctly when creating a new apikit project. Generated UI in Mule properties editors for Modules that use Map> type of structures such as MongoDB will not work. Validation error when required attribute is written with double quotes in a Choice expression. XML Metadata is not generated correctly when the provided sample has namespaces. Mule modules needs to provide icons, today many of the modules have the generic icon. See Troubleshooting Issues with Your Default OS Browser for more information. If your default internet browser does not display this content correctly, you can configure Anypoint Studio to use a Mozilla/XULRunner runtime environment as the underlying renderer for the Web UI. To be able to deploy a project which uses the runtime 4.0.0 into Cloudhub you need to have certain permissions in your Anypoint Platform user to see runtime 4.0.0 when deploying it.Īnypoint 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. Some existing features in Studio 6.x are not yet supported in Studio 7: Domains, Custom Policies, APISync, Anypoint Private Cloud, Gateway runtime connectivity. STUDIO-9522ĭependencies are not refreshed properly if the pom is updated while the dependencies are being resolved.STUDIO-9540įirst time you create a MUnit test from a Flow you get a message saying that you have to wait for the dependencies to be added to the project and then try again. Metadata tree is not being updated for Flows. Metadata: can not create XML types from samples that contains CDATA STUDIO-9436Īpplication-types file is not updated when deleting MP from XML view. Simplified experience to manage credentials when logging into the Anypoint PlatformĭataWeave editor does not support regex as function parameters STUDIO-9069 Improved user experience for connector and modules Support for importing API specifications from Design Center Additionally, every project now has a Maven POM, making it easier to incorporate projects into CI/CD systems.ĭataSense metadata is now stored in a human readable format this is easier to share, commit and merge.
Maven is now embedded out of the box inside Studio. Users can now explicitly manage which connectors and modules are associated with a project.Ĭonnectors and modules are now managed directly by Anypoint Studio, and do not require users to manage update sites.Įasily navigate to code from visual view by right clicking on a component and clicking “View XML” Improved palette which enables users to more quickly discover what they’re looking for by searching directly for operations and saving favorites
0 kommentar(er)
