Dependency-updates (#85)

* dependency-updates

Author: jakobbraun

.github/workflows/broken_links_checker.yml

@@ -10,8 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2
-      - name: lychee Link Checker
-        id: lc
-        uses: lycheeverse/[email protected]
-      - name: Fail if there were link errors
-        run: exit ${{ steps.lc.outputs.exit_code }}
+      - uses: gaurav-nelson/github-action-markdown-link-check@v1
+        with:
+          use-quiet-mode: 'yes'
+          use-verbose-mode: 'yes'

.github/workflows/ci-build.yml

@@ -0,0 +1,30 @@
+name: CI Build
+
+on:
+  - push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout the repository
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+      - name: Set up JDK 11
+        uses: actions/setup-java@v1
+        with:
+          java-version: 11
+      - name: Cache local Maven repository
+        uses: actions/cache@v2
+        with:
+          path: ~/.m2/repository
+          key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
+          restore-keys: |
+            ${{ runner.os }}-maven-
+      - name: Run tests and build with Maven
+        run: mvn --batch-mode --update-snapshots clean verify sonar:sonar --file pom.xml -DtrimStackTrace=false -Dsonar.organization=exasol -Dsonar.host.url=https://sonarcloud.io -Dsonar.login=$SONAR_TOKEN
+        env:
+          GITHUB_OAUTH: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

.github/workflows/release_droid_upload_github_release_assets.yml

@@ -32,4 +32,9 @@ jobs:
         uses: shogo82148/actions-upload-release-asset@v1
         with:
           upload_url: ${{ github.event.inputs.upload_url }}
-          asset_path: target/*.jar
+          asset_path: target/*.jar
+      - name: Upload error-code-report
+        uses: shogo82148/actions-upload-release-asset@v1
+        with:
+          upload_url: ${{ github.event.inputs.upload_url }}
+          asset_path: target/error_code_report.json

.travis.yml

@@ -1,10 +1,8 @@
 # Test Database Builder Java
 
-[![Build Status](https://travis-ci.com/exasol/test-db-builder-java.svg?branch=main)](https://travis-ci.com/exasol/test-db-builder-java)
+[![Build Status](https://github.com/exasol/test-db-builder-java/actions/workflows/ci-build.yml/badge.svg)](https://github.com/exasol/test-db-builder-java/actions/workflows/ci-build.yml)
 [![Maven Central](https://img.shields.io/maven-central/v/com.exasol/test-db-builder-java)](https://search.maven.org/artifact/com.exasol/test-db-builder-java)
 
-SonarCloud results:
-
 [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=com.exasol%3Atest-db-builder-java&metric=alert_status)](https://sonarcloud.io/dashboard?id=com.exasol%3Atest-db-builder-java)
 
 [![Security Rating](https://sonarcloud.io/api/project_badges/measure?project=com.exasol%3Atest-db-builder-java&metric=security_rating)](https://sonarcloud.io/dashboard?id=com.exasol%3Atest-db-builder-java)

README.md

@@ -59,13 +59,13 @@
 
 [31]: https://www.eclemma.org/jacoco/index.html
 [51]: https://github.com/exasol/project-keeper-maven-plugin
-[25]: LICENSE-exasol-jdbc.txt
 [2]: https://github.com/exasol/error-reporting-java
 [0]: https://github.com/exasol/db-fundamentals-java
 [27]: https://jdbc.postgresql.org
 [23]: http://www.apache.org/licenses/LICENSE-2.0.txt
 [29]: https://maven.apache.org/surefire/maven-surefire-plugin/
 [55]: http://www.sonatype.com/public-parent/nexus-maven-plugins/nexus-staging/nexus-staging-maven-plugin/
+[25]: https://www.exasol.com/support/secure/attachment/155343/EXASOL_SDK-7.0.11.tar.gz
 [28]: https://jdbc.postgresql.org/about/license.html
 [61]: http://maven.apache.org/plugins/maven-clean-plugin/
 [1]: https://opensource.org/licenses/MIT

dependencies.md

@@ -1,10 +1,11 @@
 # Changes
 
+* [3.2.1](changes_3.2.1.md)
 * [3.2.0](changes_3.2.0.md)
 * [3.1.1](changes_3.1.1.md)
 * [3.1.0](changes_3.1.0.md)
 * [3.0.0](changes_3.0.0.md)
 * [2.1.0](changes_2.1.0.md)
 * [2.0.0](changes_2.0.0.md)
 * [1.1.0](changes_1.1.0.md)
-* [1.0.1](changes-1.0.1.md)
+* [1.0.1](changes_1.0.1.md)

doc/changes/changelog.md

@@ -0,0 +1,34 @@
+# Test Database Builder for Java 3.2.1, released 2021-08-02
+
+Code name: Dependency Updates
+
+## Summary
+
+In this release we updated the dependencies. By that we fixed transitive CVE-2021-36090.
+
+## Dependency Updates
+
+### Compile Dependency Updates
+
+* Updated `com.exasol:db-fundamentals-java:0.1.1` to `0.1.2`
+
+### Runtime Dependency Updates
+
+* Updated `com.exasol:exasol-jdbc:7.0.7` to `7.0.11`
+* Updated `mysql:mysql-connector-java:8.0.25` to `8.0.26`
+* Updated `org.postgresql:postgresql:42.2.20.jre7` to `42.2.23.jre7`
+
+### Test Dependency Updates
+
+* Updated `com.exasol:exasol-testcontainers:3.5.3` to `4.0.0`
+* Updated `com.exasol:hamcrest-resultset-matcher:1.4.0` to `1.4.1`
+* Updated `nl.jqno.equalsverifier:equalsverifier:3.6.1` to `3.7`
+* Updated `org.mockito:mockito-junit-jupiter:3.11.0` to `3.11.2`
+* Updated `org.testcontainers:junit-jupiter:1.15.3` to `1.16.0`
+* Updated `org.testcontainers:mysql:1.15.3` to `1.16.0`
+* Updated `org.testcontainers:postgresql:1.15.3` to `1.16.0`
+
+### Plugin Dependency Updates
+
+* Updated `com.exasol:error-code-crawler-maven-plugin:0.1.1` to `0.5.1`
+* Updated `com.exasol:project-keeper-maven-plugin:0.7.2` to `0.10.0`

doc/changes/changes_3.2.1.md

@@ -28,6 +28,7 @@ Please refer to the [System Requirement Specification](system_requirements.md) f
 This section introduces the building blocks of the software. Together those building blocks make up the big picture of the software structure.
 
 ## `ExasolObjectFactory`
+
 `dsn~exasol-object-factory~1`
 
 The `ExasolObjectFactory` is a factory that allows users to create Exasol-specific database objects.
@@ -39,6 +40,7 @@ Covers:
 Needs: impl, itest
 
 ## `MySqlObjectFactory`
+
 `dsn~mysql-object-factory~1`
 
 The `MySqlObjectFactory` is a factory that allows users to create MySQL-specific database objects.
@@ -56,6 +58,7 @@ This section describes the runtime behavior of the software.
 ## Creating Database Objects
 
 ### Creating Database Users
+
 `dsn~creating-database-users~1`
 
 Users can create database users by providing a username and a password.
@@ -67,6 +70,7 @@ Covers:
 Needs: impl, utest, itest
 
 ### Creating Adapter Scripts
+
 `dsn~creating-adapter-scripts~1`
 
 Users can create Exasol adapter scripts.
@@ -77,11 +81,11 @@ Covers:
 
 Needs: impl, utest, itest
 
-### Creating Exasol Objects With JVM Options 
+### Creating Exasol Objects With JVM Options
+
 `dsn~creating-exasol-java-object-with-jvm-options~1`
 
-Users can create virtual schema adapters and UDFs with JVM options.
-They can set these options globally and TDDB will add them to all JAVA adapters and scripts.
+Users can create virtual schema adapters and UDFs with JVM options. They can set these options globally and TDDB will add them to all JAVA adapters and scripts.
 
 Rationale: By that users can for example add a debugger or profiler to all JAVA scripts.
 
@@ -92,6 +96,7 @@ Covers:
 Needs: impl, utest
 
 ### Creating Connection
+
 `dsn~creating-connections~1`
 
 Users can create Exasol connection definitions.
@@ -103,6 +108,7 @@ Covers:
 Needs: impl, utest, itest
 
 ### Creating Schemas
+
 `dsn~creating-schemas~1`
 
 Users can create dialect specific schemas.
@@ -114,6 +120,7 @@ Covers:
 Needs: impl, utest, itest
 
 ### Creating Virtual Schemas
+
 `dsn~creating-virtual-schemas~1`
 
 Users can create exasol virtual schemas.
@@ -125,6 +132,7 @@ Covers:
 Needs: impl, utest, itest
 
 ### Creating Tables
+
 `dsn~creating-tables~1`
 
 Users can create tables.
@@ -136,6 +144,7 @@ Covers:
 Needs: impl, utest, itest
 
 ### Granting System Privileges to Database Users
+
 `dsn~granting-system-privileges-to-database-users~1`
 
 Users can select and grant System Privileges to created database users from the list of supported System Privileges.
@@ -147,6 +156,7 @@ Covers:
 Needs: impl, utest, itest
 
 ### Creating Scripts
+
 `dsn~creating-scripts~1`
 
 Users can create script objects from inside schema objects by providing the script content programmatically.
@@ -158,6 +168,7 @@ Covers:
 Needs: impl, itest
 
 ### Creating UDFs
+
 `dsn~creating-udfs~1`
 
 Users can create UDF objects from inside schema objects by providing the script from file.
@@ -169,6 +180,7 @@ Covers:
 Needs: impl, itest
 
 ### Creating Scripts from Files
+
 `dsn~creating-scripts-from-files~1`
 
 Users can create scripts from inside a schema object by loading the script contents from a file.
@@ -180,9 +192,10 @@ Covers:
 Needs: impl, itest
 
 ### Creating Object Through SQL Files
+
 `dsn~creating-objects-through-sql-files~1`
 
-Users can create database objects by executing the statements in an SQL file. 
+Users can create database objects by executing the statements in an SQL file.
 
 Covers:
 
@@ -195,6 +208,7 @@ Needs: impl, itest
 ## Running Executable Database Content
 
 ### Running Scripts That Have no Return
+
 `dsn~running-scripts-that-have-no-return~1`
 
 Users can execute scripts directly from a script Java object.
@@ -208,6 +222,7 @@ Needs: impl, itest
 ## Controlling Existing Database Objects
 
 ### Controlling Existing Scripts
+
 `dsn~controlling-existing-scripts~1`
 
 Users get a control object for a script from within a schema by specifying the existing scripts name.
@@ -222,6 +237,7 @@ Needs: impl, itest
 ## Dropping database objects
 
 ### Dropping Users
+
 `dsn~dropping-users~1`
 
 Users can drop database users using TDDB.
@@ -233,6 +249,7 @@ Covers:
 Needs: impl, itest
 
 ### Dropping Tables
+
 `dsn~dropping-tables~1`
 
 Users can drop tables using TDDB.
@@ -244,6 +261,7 @@ Covers:
 Needs: impl, itest
 
 ### Dropping Schemas
+
 `dsn~dropping-schemas~2`
 
 Users can drop schemas using TDDB.
@@ -257,6 +275,7 @@ Covers:
 Needs: impl, itest
 
 ### Dropping Adapter Scripts
+
 `dsn~dropping-adapter-scripts~1`
 
 Users can drop adapter scripts using TDDB.
@@ -268,6 +287,7 @@ Covers:
 Needs: impl, itest
 
 ### Dropping Connections
+
 `dsn~dropping-connections~1`
 
 Users can drop connections using TDDB.
@@ -279,6 +299,7 @@ Covers:
 Needs: impl, itest
 
 ### Dropping Scripts
+
 `dsn~dropping-scripts~1`
 
 Users can drop scripts using TDDB.
@@ -290,6 +311,7 @@ Covers:
 Needs: impl, itest
 
 ### Dropping UDFs
+
 `dsn~dropping-udfs~1`
 
 Users can drop UDFs using TDDB.
@@ -301,6 +323,7 @@ Covers:
 Needs: impl, itest
 
 ### Dropping Virtual Schemas
+
 `dsn~dropping-virtual-schemas~2`
 
 Users can drop virtual schemas using TDDB.
@@ -319,7 +342,7 @@ Needs: impl, itest
 
 ## How Do we Let Users Attach to Existing Database Object
 
-As explained in [the system requirements section "Controlling Existing Database Objects"](system_requirements#Controlling-existing-database-objects), sometimes users need to control existing database objects in integration tests.
+As explained in [the system requirements section "Controlling Existing Database Objects"](system_requirements.md#Controlling-existing-database-objects), sometimes users need to control existing database objects in integration tests.
 
 The decision on how to do this is architecture relevant because it impacts usability, code maintainability (both of the TDDB and integration tests written with it) and safety of the created code.
 
@@ -336,6 +359,7 @@ Depending on the type of the object this can require administrative privileges.
 ### Decisions
 
 #### Attaching to Existing Database Object by Name
+
 `dsn~attaching-to-existing-database-object-by-name~1`
 
 When users attach to an existing database object, all they need is a fully-qualified name. The control object holds no metadata of that object.