update action number and fix maven target dir

Author: maliparasoft

README.md

@@ -87,7 +87,7 @@ jobs:
     
     # Checks out your repository under $GITHUB_WORKSPACE, so that your job can access it.
     - name: Checkout repository
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3
       
     # Generates the jtest.data.json input file.
     - name: Create input for Jtest
@@ -96,25 +96,25 @@ jobs:
     # Runs code analysis with Jtest.
     - name: Run Jtest
       id: jtest
-      uses: parasoft/run-jtest-action@1.0.0
+      uses: parasoft/run-jtest-action@2.0.0
       with:
         #Uses the jtest.data.json generated with the Gradle command in the previous step
         input: build/jtest/jtest.data.json
 
     # Uploads analysis results in the SARIF format, so that they are displayed as GitHub code scanning alerts.
     - name: Upload results (SARIF)
-        if: always()
-        uses: github/codeql-action/upload-sarif@v2
-        with:
-            sarif_file: reports/report.sarif # reports is a default location for reports directory
+      if: always()
+      uses: github/codeql-action/upload-sarif@v2
+      with:
+        sarif_file: reports/report.sarif # reports is a default location for reports directory
 
     # Uploads an archive that includes all report files (.xml, .html, .sarif).
     - name: Archive reports
-        if: always()
-        uses: actions/upload-artifact@v2
-        with:
-          name: Static analysis reports
-          path: reports/*.*
+      if: always()
+      uses: actions/upload-artifact@v3
+      with:
+        name: Static analysis reports
+        path: reports/*.*
 
 ```
 
@@ -148,7 +148,7 @@ jobs:
     
     # Checks out your repository under $GITHUB_WORKSPACE, so that your job can access it.
     - name: Checkout repository
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3
     
     # Generates the jtest.data.json input file.
     - name: Create input for Jtest
@@ -157,25 +157,25 @@ jobs:
     # Runs code analysis with Jtest
     - name: Run Jtest
       id: jtest
-      uses: parasoft/run-jtest-action@1.0.0
+      uses: parasoft/run-jtest-action@2.0.0
       with:
         #Uses the jtest.data.json generated with the Maven command in the previous step
-        input: build/jtest/jtest.data.json
+        input: target/jtest/jtest.data.json
 
     # Uploads analysis results in the SARIF format, so that they are displayed as GitHub code scanning alerts.
     - name: Upload results (SARIF)
-        if: always()
-        uses: github/codeql-action/upload-sarif@v2
-        with:
-            sarif_file: reports/report.sarif # reports is a default location for reports directory
+      if: always()
+      uses: github/codeql-action/upload-sarif@v2
+      with:
+        sarif_file: reports/report.sarif # reports is a default location for reports directory
 
     # Uploads an archive that includes all report files (.xml, .html, .sarif).
     - name: Archive reports
-        if: always()
-        uses: actions/upload-artifact@v2
-        with:
-          name: Static analysis reports
-          path: reports/*.*
+      if: always()
+      uses: actions/upload-artifact@v3
+      with:
+        name: Static analysis reports
+        path: reports/*.*
 
 ```
 
@@ -192,7 +192,7 @@ If `jtestcli` executable is not on `PATH`, you can configure the path to the ins
 
 ```yaml
 - name: Run Jtest
-  uses: parasoft/run-jtest-action@1.0.0
+  uses: parasoft/run-jtest-action@2.0.0
   with:
     installDir: '/opt/parasoft/jtest'
 ```
@@ -202,7 +202,7 @@ You can configure the `input` parameter to provide the path to a JSON file that
 
 ```yaml
 - name: Run Jtest
-  uses: parasoft/run-jtest-action@1.0.0
+  uses: parasoft/run-jtest-action@2.0.0
   with:
     input: 'build/demo.data.json'
 ```
@@ -212,7 +212,7 @@ Code analysis with Jtest is performed by using a test configuration - a set of s
 To specify a test configuration directly in your workflow, add the `testConfig` parameter to the `Run Jtest` action and specify the URL of the test configuration you want to use:
 ```yaml
 - name: Run Jtest
-  uses: parasoft/run-jtest-action@1.0.0
+  uses: parasoft/run-jtest-action@2.0.0
   with:
     testConfig: 'builtin://Recommended Rules'
 ```
@@ -221,7 +221,7 @@ To specify a test configuration directly in your workflow, add the `testConfig`
 Generating reports in the SARIF format is available in Jtest since version 2021.1. If you are using an earlier Jtest version, you need to customize the `Run Jtest` action to enable generating SARIF reports:
 ```yaml
 - name: Run Jtest
-  uses: parasoft/run-jtest-action@1.0.0
+  uses: parasoft/run-jtest-action@2.0.0
   with:
     reportFormat: xml,html,custom
     additionalParams: '-property report.custom.extension=sarif -property report.custom.xsl.file=${PARASOFT_SARIF_XSL}'