In order to support auto inference for document virtual schemas (see exasol/virtual-schema-common-document#155) it must be possible to omit the "mapping" field of an EDML definition.

Remove repository maven.exasol.com and Update dependencies

edml-java depends on com.github.everit-org.json-schema:org.everit.json.schema:jar:1.14.1:compile which was published with different maven coordinates and to different repositories in the past.Some seem to have been copied to maven.exasol.com.

See https://github.com/everit-org/json-schema

• Version >= 1.9.2 available on Maven Central, e.g. 1.14.1
• version 1.6.0 until 1.9.1 available only on JitPack.
• versions <= 1.5.1 available on Maven Central.

When deserializing a ToTimestampMapping from JSON, class ToTimestampMappingDeserializer always uses the default value (true) for property useTimestampWithLocalTimezoneType.

add support for additional configuration (in this case on the file level)

Add language to file release_config.yml .. to avoid RD warning:

[WARNING] W-RD-REP-34: The repository language was detected automatically as 'JAVA'. If incorrect then please add language: to file release_config.yml or use command line argument -lg .

Exract the EDML part from virtual-schema-common-document-files.
See: exasol/virtual-schema-common-document#134

After setting required maven version to 3.8.7. or higher with PK ticket #444 (project-keeper release 2.9.6) users can remove the suppressed warning from file .project-keeper.yml:

  - regex: "(?s)E-PK-CORE-53: The dependencies.md file has outdated content.*"

Affected repositories:

• spark-connector
• ci-isolation-aws
• error-catalog
• cloudwatch-adapter
• tableau-connector
• parquet-io-java
• virtual-schema-common-document
• parquet-edml-generator
• cloudwatch-dashboard-examples
• glue-connector
• exasol-virtual-schema
• ✅ project-keeper
• s3-document-files-virtual-schema
• cloud-storage-extension
• extension-manager
• java-class-list-extractor
• edml-java

Data type TIMESTAMP WITH LOCAL TIME ZONE does not make sense for document based virtual schemas that don't support time zones at all. So we decided to drop support completely.

Please note that property ToTimestampMapping.useTimestampWithLocalTimezoneType was implemented but not documented anywhere. It will be removed completely now.

This project uses lombok which makes the build more complicated and conflicts with adding a module-info.java file.
That's why we should remove it from the project.

Dependency org.json has a vulnerability:

[ERROR] Failed to execute goal org.sonatype.ossindex.maven:ossindex-maven-plugin:3.2.0:audit (default-cli) on project edml-java: Detected 1 vulnerable components:
[ERROR]   org.json:json:jar:20220320:compile; https://ossindex.sonatype.org/component/pkg:maven/org.json/json@20220320?utm_source=ossindex-client&utm_medium=integration&utm_content=1.8.1
[ERROR]     * [CVE-2022-45688] CWE-787: Out-of-bounds Write (7.5); https://ossindex.sonatype.org/vulnerability/CVE-2022-45688?component-type=maven&component-name=org.json%2Fjson&utm_source=ossindex-client&utm_medium=integration&utm_content=1.8.1

We should replace it with jakarta json library.