Merge pull request #5 from vectorgrp/release-v2.2.x

OCS Domain Plugin Release v2.2.0

Author: arora-pratham

.gitignore

@@ -4,4 +4,4 @@
 /buildSrc/.gradle
 /buildSrc/build
 /plugins/*/build
-
+/_bswmd/build

README.md

@@ -19,62 +19,58 @@ Furthermore, it allows the extension of the existing functionality.
 ## Getting Started
 The MICROSAR Automation SDK offers everything that is needed to build an OCS Custom App and the Domain Plugins. It
 can be downloaded from the Vector Download Center in the 
-[DaVinci Team](https://www.vector.com/de/de/support-downloads/download-center/#product=%5B%2251284%22%5D&tab=1&pageSize=15&sort=date&order=desc) product category.
+[DaVinci Team](https://www.vector.com/de/de/support-downloads/download-center/#product=%5B%2271683%22%5D&tab=1&pageSize=15&sort=date&order=desc) product category.
 Most important artifact which is required from the MICROSAR Automation SDK is the so called OCS Core. For more 
 information we strongly recommend to read the contained documentation.
 
 ### Preparation
 For simplification of the build setup we recommend as a first step to arrange the required files and folders as follows:  
 ```
 ├── BswPackage
-|   └── MICROSAR_Classic_R31
+|   └── MICROSAR_Classic_R35
 |   |   └── Components
-|   |   └── DaVinciConfigurator
-|   |   └── ...
-|   └── MICROSAR_Classic_R33
-|   |   └── Components
-|   |   └── DaVinciConfigurator
 |   |   └── ...
 ├── ocs-custom-app
 ├── ocs-domain-plugins
 └── repository
 ```
-Within the BswPackage folder different MICROSAR Classic BSW Package releases can be stored. In this cases one for R31
-and one for R33. The ocs-custom-app and the repository folder are both part of the MICROSAR Automation SDK. The
-ocs-domain-plugins directory contains the content of this repository. Arranging the folder in this way will simplify the
-customization of the gradle properties.
+Within the BswPackage folder different MICROSAR Classic BSW Package releases can be stored. In this cases one for R35.  
+The ocs-custom-app and the repository folder are both part of the MICROSAR Automation SDK. The ocs-domain-plugins directory  
+contains the content of this repository. Arranging the folder in this way will simplify the customization of the gradle properties.
 
 ### Customization of the Gradle properties
 Within the `ocs-domain-plugins` folder you can find the `gradle.properties` file:
 ```
 #localSipStore=path/to/sip/store/directory
 #localSip=path/to/used/sip/external
 ocsRepo=../repository
-
-vOcsCore=1.7.0
-vPluginsCommon=1.5.0
-vOcsCom=1.8.0
-vOcsDiag=1.8.0
-vOcsNvM=1.8.0
-vOcsEcuState=1.8.0
-vOcsRuntime=1.8.0
-vOcsSecurity=1.6.0
+#cfg6=path/to/davinci configurator/directory
+
+vOcsCore=3.1.0
+vPluginsCommon=2.2.0
+vOcsCom=2.2.0
+vOcsDiag=2.2.0
+vOcsNvM=2.2.0
+vOcsEcuState=2.2.0
+vOcsRuntime=2.2.0
+vOcsSecurity=2.2.0
 ```
 Based on the folder structure example above the explanation of the properties becomes easier. 
 Adapt the properties as following:
 ```
 localSipStore=D:/dev/ocs/BswPackages
-localSip=MICROSAR_Classic_R31
+localSip=MICROSAR_Classic_R35
 ocsRepo=../repository
-
-vOcsCore=1.7.0
-vPluginsCommon=my-company-1.5.0
-vOcsCom=my-company-1.8.0
-vOcsDiag=my-company-1.8.0
-vOcsNvM=my-company-1.8.0
-vOcsEcuState=my-company-1.8.0
-vOcsRuntime=my-company-1.8.0
-vOcsSecurity=my-company-1.6.0
+cfg6=<installation path of DaVinci Configurator Classic 6.2>
+
+vOcsCore=3.1.0
+vPluginsCommon=my-company-2.2.0
+vOcsCom=my-company-2.2.0
+vOcsDiag=my-company-2.2.0
+vOcsNvM=my-company-2.2.0
+vOcsEcuState=my-company-2.2.0
+vOcsRuntime=my-company-2.2.0
+vOcsSecurity=my-company-2.2.0
 ```
 The `localSipStore` should point to the root directory of the BSW Packages while the `localSip` itself mentions a 
 dedicated BSW Package against which the source code will be compiled. The gradle project of the `ocs-custom-app` and
@@ -86,8 +82,8 @@ We kindly ask you to adapt the version information mentioned in the `gradle.prop
 that the plugins you build by yourself can be distinguished from those delivered as pre-build artifacts in the MICROSAR
 Automation SDK. Here an example for the resulting files:
 ```groovy
-ocs-communication-plugin-1.7.0.jar            // without adaptions
-ocs-communication-plugin-my-company-1.7.0.jar // with adaptions
+ocs-communication-plugin-2.2.0.jar            // without adaptions
+ocs-communication-plugin-my-company-2.2.0.jar // with adaptions
 ```
 
 ### Build the OCS Domain Plugins
@@ -112,7 +108,7 @@ above. Reason for this is a simple conceptional decision that this `repository`
 delivered by Vector. In most cases, local maven repository which is used for the publication can be found under you
 Windows user account, for example:
 ```batch
-C:\Users\<your user account>\.m2\repository\com\vector\ocs\plugins\ocs-communication-plugin\my-company-1.7.0\ocs-communication-plugin-my-company-1.7.0.jar
+C:\Users\<your user account>\.m2\repository\com\vector\ocs\plugins\ocs-communication-plugin\my-company-2.2.0\ocs-communication-plugin-my-company-2.2.0.jar
 ```
 
 ## Building an OCS Custom App
@@ -123,33 +119,35 @@ file:
 #localSipStore=path/to/sip/store/directory
 #localSip=path/to/used/sip/
 ocsRepo=../repository
-
-vOcsCore=2.2.0
-vPluginsCommon=1.5.0
-vOcsCom=1.8.0
-vOcsDiag=1.8.0
-vOcsNvM=1.8.0
-vOcsEcuState=1.8.0
-vOcsRuntime=1.8.0
-vOcsSecurity=1.6.0
+#cfg6=path/to/davinci configurator/directory
+
+vOcsCore=3.1.0
+vPluginsCommon=2.2.0
+vOcsCom=2.2.0
+vOcsDiag=2.2.0
+vOcsNvM=2.2.0
+vOcsEcuState=2.2.0
+vOcsRuntime=2.2.0
+vOcsSecurity=2.2.0
 ```
 The `localSipStore`, `localSip` and `ocsRepo` should be configured in the same way as for the `ocs-domain-plugins`.
 If you keep the other version numbers as stated in the file you would build the OCS Custom App based on the Vector
 pre-build artifacts. In fact, you want to use the plugins you built by yourself, therefore you also need to adapt those
 properties, so that the result looks as follows:
 ```
 localSipStore=D:/dev/ocs/BswPackages
-localSip=MICROSAR_Classic_R31
+localSip=MICROSAR_Classic_R35
 ocsRepo=../repository
-
-vOcsCore=1.7.0
-vPluginsCommon=my-company-1.5.0
-vOcsCom=my-company-1.8.0
-vOcsDiag=my-company-1.8.0
-vOcsNvM=my-company-1.8.0
-vOcsEcuState=my-company-1.8.0
-vOcsRuntime=my-company-1.8.0
-vOcsSecurity=my-company-1.6.0
+cfg6=<installation path of DaVinci Configurator Classic 6.2>
+
+vOcsCore=3.1.0
+vPluginsCommon=my-company-2.2.0
+vOcsCom=my-company-2.2.0
+vOcsDiag=my-company-2.2.0
+vOcsNvM=my-company-2.2.0
+vOcsEcuState=my-company-2.2.0
+vOcsRuntime=my-company-2.2.0
+vOcsSecurity=my-company-2.2.0
 ```
 Please note that the gradle project of the OCS Custom App is prepared in a way that it handles the ocsRepo as well as
 the local maven repository.
@@ -171,15 +169,16 @@ Beside the mentioned dependencies the shared gradle project may point to additio
 
 | External Tool | Description |
 |---------------|-------------|
-| JAVA JDK      | 1.8         |
-| Gradle        | 8.13        |
+| JAVA JDK      | 21.0        |
+| Gradle        | 8.14.3      |
 
 ## Release Information
 | Release | Belongs to                     | Supports MICROSAR Classic Releases | 
 |---------|--------------------------------|------------------------------------|
 | v1.6.0  | MICROSAR Automation SDK v1.5.0 | R31 - R34                          |
 | v1.7.0  | MICROSAR Automation SDK v1.6.0 | R31 - R34                          |
 | v1.8.0  | MICROSAR Automation SDK v1.7.0 | R31 - R34                          |
+| v2.2.0  | MICROSAR Automation SDK v2.0.0 | R35                                |
 
 ## Abbreviations
 | Abbreviation | Description                       |