Merge pull request #65 from mulesoft/W-11585544-update-studio-version-3.9

sathya0 · web-flow · commit 62fdf8cb5c27 · 2022-08-11T14:59:49.000-07:00
W-11585544: Update Studio version
diff --git a/modules/ROOT/pages/adding-datasense-query-language.adoc b/modules/ROOT/pages/adding-datasense-query-language.adoc
@@ -14,7 +14,7 @@ image::6-package.png[]
 
 == Prerequisites
 
-* Familiarity with Anypoint Connectors, xref:5@studio::datasense.adoc[DataSense], xref:5@studio::datasense-query-editor.adoc[DataSense Query Editor], and xref:adding-datasense-query-language.adoc[Adding DataSense Query Language] from a user level.
+* Familiarity with Anypoint Connectors, xref:5.x@studio::datasense.adoc[DataSense], xref:5.x@studio::datasense-query-editor.adoc[DataSense Query Editor], and xref:adding-datasense-query-language.adoc[Adding DataSense Query Language] from a user level.
 * Understand Java "@" annotations. See http://mulesoft.github.io/mule-devkit/[Anypoint DevKit API Reference].
 * Experience with implementing a basic connector with xref:index.adoc[Anypoint DevKit].
 * Understand the visitor pattern, which is fundamental to the workings of DSQL-to-native query language translation.
diff --git a/modules/ROOT/pages/adding-datasense.adoc b/modules/ROOT/pages/adding-datasense.adoc
@@ -12,7 +12,7 @@ image::devkit-steps-operations.png[]
 
 == Prerequisites
 
-This document assumes that you are familiar with the connector architecture presented in xref:index.adoc[Anypoint Connector DevKit], and that you are familiar with xref:5@studio::datasense.adoc[DataSense] from an end-user's perspective.
+This document assumes that you are familiar with the connector architecture presented in xref:index.adoc[Anypoint Connector DevKit], and that you are familiar with xref:5.x@studio::datasense.adoc[DataSense] from an end-user's perspective.
 
 == Connectors with DataSense
 
@@ -24,7 +24,7 @@ DataSense provides entities and their internal structure to Studio, which, in tu
 * Use DataWeave's ability to automatically infer the input or output data within a mapping (when used in conjunction with a connector that is DataSense-enabled).
 
 [NOTE]
-The *fundamental advantage of DataSense* is the ability to extract metadata from the data model exposed by an application through the connector. Learn more about xref:5@studio::datasense.adoc[DataSense].
+The *fundamental advantage of DataSense* is the ability to extract metadata from the data model exposed by an application through the connector. Learn more about xref:5.x@studio::datasense.adoc[DataSense].
 
 The two key steps to implementing DataSense are:
 
diff --git a/modules/ROOT/pages/connector-attributes-and-operations.adoc b/modules/ROOT/pages/connector-attributes-and-operations.adoc
@@ -24,7 +24,7 @@ More details can be found in xref:defining-connector-attributes.adoc[Defining Co
 
 == Static Versus Dynamic Data Models
 
-The underlying data model for the API you connect to often drives design decisions about the best way to represent data going to and from your connector. The goal in general is to choose a representation that fits the underlying data, while still supporting the necessary metadata to work with xref:5@studio::datasense.adoc[DataSense].
+The underlying data model for the API you connect to often drives design decisions about the best way to represent data going to and from your connector. The goal in general is to choose a representation that fits the underlying data, while still supporting the necessary metadata to work with xref:5.x@studio::datasense.adoc[DataSense].
 
 * *Static data models* have fixed definitions of all the objects and their attributes supported by the target. Most services, particularly relatively simple ones, implement static data models. For APIs using static data models, it is recommended to create Plain Old Java Objects (POJOs) that correspond to the objects exposed through the connector's operations. Short of a revision to the target APIs, these classes do not need to change in individual deployments.
 * *Dynamic data models* enable the customization of the application objects and their attributes. Complex ERP applications often implement dynamic data models so that they can be customized from one customer to the next. In the case of a dynamic data model, it is recommended that you use Java key-value Maps to represent application objects in Mule.
diff --git a/modules/ROOT/pages/developing-devkit-connector-tests.adoc b/modules/ROOT/pages/developing-devkit-connector-tests.adoc
@@ -15,7 +15,7 @@ While testing strategy may vary extensively based on your specific needs, this d
 This document assumes that you:
 
 * Installed the Anypoint Connector DevKit Plugin as described in  xref:creating-an-anypoint-connector-project.adoc[Creating an Anypoint Connector Project]
-* Are familiar with xref:5@studio::index.adoc[Anypoint Studio]
+* Are familiar with xref:5.x@studio::index.adoc[Anypoint Studio]
 * Are familiar with https://maven.apache.org/[Maven] build manager for Java
 * Are familiar with http://junit.org/[JUnit]
 
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
@@ -32,7 +32,7 @@ _Existing Connector:_
 See also xref:creating-a-soap-connector.adoc[Creating a SOAP Connector].
 . xref:setting-up-api-access.adoc[Determine resource access] - Each resource has a different access method, such as REST, SOAP, FTP, or the Java SDK features.
 . xref:authentication.adoc[Choose an authentication mechanism] - Mule supports OAuth V1 or V2, and username and password authentication (known as xref:connection-management.adoc[connection management]), which can be used for protocols such as API Key, SAML, NTLM, Kerberos, or LDAP.
-. xref:connector-attributes-and-operations.adoc[Choose the connector's data model] - Models can be static Java objects or dynamic objects. You can use xref:5@studio::datasense.adoc[DataSense] - Determine what information the target resource expects.
+. xref:connector-attributes-and-operations.adoc[Choose the connector's data model] - Models can be static Java objects or dynamic objects. You can use xref:5.x@studio::datasense.adoc[DataSense] - Determine what information the target resource expects.
 . xref:defining-connector-attributes.adoc[Add connector @ attribute annotations] - Create code for your connector containing the @ attributes that Mule uses to designate the important parts of your connector.
 . xref:developing-devkit-connector-tests.adoc[Code tests] - Tests can be unit tests, functional tests, and Studio interoperability tests.
 . xref:connector-reference-documentation.adoc[Document your connector] - MuleSoft provides a template that helps you fill in the blanks to create documentation to help your staff and others understand the features and use of your connector.
@@ -283,4 +283,4 @@ The `pom.xml` file for a DevKit 3.9 project. The `<parent>` section shows DevKit
 * xref:3.9@mule-runtime::anypoint-connectors.adoc[Anypoint Connectors]
 * https://www.anypoint.mulesoft.com/exchange/?type=connector[Connectors on Exchange]
 * http://blogs.mulesoft.com/dev/anypoint-studio-dev/change-the-studio-category-of-your-devkit-component/[Blog post on how to change the DevKit extension category]
-* xref:6@studio::datasense-enabled-connectors.adoc[DataSense-Enabled Connectors]
+* xref:6.x@studio::datasense-enabled-connectors.adoc[DataSense-Enabled Connectors]
diff --git a/modules/ROOT/pages/multiple-level-datasense-support.adoc b/modules/ROOT/pages/multiple-level-datasense-support.adoc
@@ -252,5 +252,5 @@ In the XML, this key is placed as a single string, where each level is separated
 
 === See Also
 
-* xref:5@studio::datasense.adoc[DataSense]
+* xref:5.x@studio::datasense.adoc[DataSense]
 * xref:adding-datasense.adoc[Adding DataSense]
diff --git a/modules/ROOT/pages/oauth-v2.adoc b/modules/ROOT/pages/oauth-v2.adoc
@@ -10,7 +10,7 @@ This page presents a detailed discussion of DevKit's support for OAuth V2 authen
 
 == Prerequisites
 
-This document assumes you are familiar with the xref:5@studio::index.adoc[Anypoint Connector Essentials] and are ready to implement authentication on your connector. It assumes you are familiar with the various xref:authentication-methods.adoc[authentication methods] and may be using OAuth V1 to authenticate with your API.
+This document assumes you are familiar with the xref:5.x@studio::index.adoc[Anypoint Connector Essentials] and are ready to implement authentication on your connector. It assumes you are familiar with the various xref:authentication-methods.adoc[authentication methods] and may be using OAuth V1 to authenticate with your API.
 
 If you are not familiar with OAuth V1 authentication, what it is or how it works, we recommend visiting http://tools.ietf.org/html/rfc5849[OAuth 1.0 protocol/RFC-5849]. Also see xref:oauth-v1.adoc[OAuth V1].
 
diff --git a/modules/ROOT/pages/setting-up-your-dev-environment.adoc b/modules/ROOT/pages/setting-up-your-dev-environment.adoc
@@ -26,7 +26,7 @@ Although you can use any Java IDE with Maven support, it's strongly recommended
 [NOTE]
 To build connector projects, you must first install the Anypoint Connector DevKit add-on into Anypoint Studio.
 
-If you have not already installed Anypoint Studio, follow the xref:3.7@mule-runtime::installing.adoc[detailed instructions] to install. For a quick introduction to Anypoint Studio, review xref:5@studio::index.adoc[Anypoint Studio Essentials].
+If you have not already installed Anypoint Studio, follow the xref:3.7@mule-runtime::installing.adoc[detailed instructions] to install. For a quick introduction to Anypoint Studio, review xref:5.x@studio::index.adoc[Anypoint Studio Essentials].
 
 == JDK
 
