Jacoco Coverage doesn't meet specified criteria if run in release mode

[rzo1]

If run in release mode

mvn release:prepare -Papache-release,apache

coverage requirements are not meet on my M3 macbook (while they seem to work correctly on GitHub actions).

This issue is created to track this behaviour.

The reason for it is, that if docker is not available (and tests are skipped), the coverage criteria is not meet and the build is failing. This should be fixed for 3.1.1 or 3.2.0.

Might be good to just put that into a profile and run that profile in CI only, so we get information about coverage or a failed build but don't get bothered while running a release on a system without docker.

[sigee]

The reason for it is, that if docker is not available (and tests are skipped), the coverage criteria is not meet and the build is failing. This should be fixed for 3.1.1 or 3.2.0.

If not all test cases are skipped and there is coverage, just not as much as in the criteria, you could decrease the threshold instead of disabling it.
But I don't understand how it relates to docker, because I could run tests without docker.

[rzo1]

Some tests aren't executed, if docker isn't available in the executing system.

[rzo1]

Guess a solution would be to decrease the thresholds to the coverage without docker (so the testcontainer tests are not executed and do not contribute to the coverage)