#193: Drop support of Spark 2.4

[benedeki]

• dropping Spark 2.4 support
• strict use of sbt projectmatrix plugin, tohave cross-builds
• basic settings moved to project/Setup.scala class
• some move or project setup code to fall into logical areas

Closes #193

[github-actions[bot]]

JaCoCo server module code coverage report - scala 2.13.11

Overall Project	76.61%	:green_apple:

There is no coverage information present for the Files changed

[lsulak]

The CI file, i.e. build instructions, must be also changed I assume, with the current setup.

Command sbt projects renders this

[info] agent_spark3 [info] agent_spark32_12 [info] * atum-service [info] database [info] model [info] model2_12 [info] server

I.e. there is no agent (one reason why CI is currently failing) and no suffix means scala 2.13 is used - otherwise, agent and model, defines 2.12 explicitly. Shouldn't we make it mode consistent? Something like

[info] agent_spark32_13 [info] agent_spark32_12 [info] * atum-service2_13 [info] database2_13 [info] model2_13 [info] model2_12 [info] server2_13

❓

--

I think that 2.13 is default = ThisBuild / scalaVersion := Setup.scala213 // default version and thus is not explicitly used for the module names. I couldn't make it work yet (the explicit suffix)

[benedeki]

The CI file, i.e. build instructions, must be also changed I assume, with the current setup.

Command sbt projects renders this

[info] agent_spark3 [info] agent_spark32_12 [info] * atum-service [info] database [info] model [info] model2_12 [info] server

I.e. there is no agent (one reason why CI is currently failing) and no suffix means scala 2.13 is used - otherwise, agent and model, defines 2.12 explicitly. Shouldn't we make it mode consistent? Something like

[info] agent_spark32_13 [info] agent_spark32_12 [info] * atum-service2_13 [info] database2_13 [info] model2_13 [info] model2_12 [info] server2_13

❓

--

I think that 2.13 is default = ThisBuild / scalaVersion := Setup.scala213 // default version and thus is not explicitly used for the module names. I couldn't make it work yet (the explicit suffix)

Yes, GitHub actions still need changes. I didn't want to hold this one back on that though. I am actually considering to make it a separate PR.